GitXplorerGitXplorer
n

Blueberry

public
3 stars
0 forks
3 issues

Commits

List of commits on branch master.
Unverified
b4303eba72ca75b68aec91b79fb8e4f43a5040fb

Require WebSocket version 13

nnarrowtux committed 12 years ago
Unverified
836553bf947f19019c6b734f450707b6789c6e33

Fixed challenge response handshake of WebSockets

committed 12 years ago
Unverified
f0fbeacd069caeeb0a85669cfc3f53e5f5fc0c5b

Fixed stack overflow when sending to an already closed connection

nnarrowtux committed 12 years ago
Unverified
a9646b02da4bba2605d336aec2b35ad33a97a973

Fixed crash when sending a frame to a broken stream

nnarrowtux committed 12 years ago
Unverified
df9b1706fa580292ed5e4586614c09f8b5bd35b3

Added onClose callback to WebSocketRequestHandler

nnarrowtux committed 12 years ago
Unverified
11ad78c47c983a55cafc45b1661bae8d73b31f78

Removed debug output

nnarrowtux committed 12 years ago

README

The README file for this repository.

Blueberry Banner

What is Blueberry?

Blueberry is a lightweight API for creating webclients for your java service.

Copyright © 2012, narrowtux

License

Blueberry is licensed under the GNU Lesser General Public License Version 3

Compiling

Blueberry uses Maven to handle its dependencies.

To compile, run mvn clean install.

Coding and Pull Request Formatting

  • Generally follow the Oracle coding standards.
  • Use tabs, no spaces.
  • No trailing whitespaces.
  • 200 column limit for readability.
  • All changes made via pull requests first be compiled locally to verify that the code does indeed compile, and tested to verify that it actually works.
  • Where practical, a test should be included to verify the change. Except in exceptional cases, bug fixes MUST include a test case which fails for the current version and passes for the updated version.
  • Commit messages must include:
    • A brief description of the change
    • A more detailed description of the change (second line and below, optional)
    • Sign-off, verifying agreement with the license terms
  • Number of commits in a pull request should be kept to one commit and all additional commits must be squashed except for circumstantial exceptions.
  • You may have more than one commit in a pull request if the commits are separate changes, otherwise squash the commits.
  • For clarification, see the full pull request guidelines.