seth
/
jam-cloud
mirror of https://bitbucket.org/jamkazam/jam-cloud.git
1
0
Fork 0
Code Issues Actions Packages Projects Releases Wiki Activity
jam-cloud/websocket-gateway
History
Seth Call a112391be1 * VRFS-438; collapsing all repos into one; requires modification of build files 2013-09-15 18:15:16 +00:00
..
bin merging websocket-gateway into websocket-gateway 2013-09-15 18:07:00 +00:00
config merging websocket-gateway into websocket-gateway 2013-09-15 18:07:00 +00:00
features merging websocket-gateway into websocket-gateway 2013-09-15 18:07:00 +00:00
lib merging websocket-gateway into websocket-gateway 2013-09-15 18:07:00 +00:00
log merging websocket-gateway into websocket-gateway 2013-09-15 18:07:00 +00:00
script/package merging websocket-gateway into websocket-gateway 2013-09-15 18:07:00 +00:00
spec merging websocket-gateway into websocket-gateway 2013-09-15 18:07:00 +00:00
.gitignore * VRFS-438; collapsing all repos into one; requires modification of build files 2013-09-15 18:15:16 +00:00
.pg_migrate merging websocket-gateway into websocket-gateway 2013-09-15 18:07:00 +00:00
.ruby-gemset merging websocket-gateway into websocket-gateway 2013-09-15 18:07:00 +00:00
.ruby-version merging websocket-gateway into websocket-gateway 2013-09-15 18:07:00 +00:00
Gemfile * VRFS-438; collapsing all repos into one; requires modification of build files 2013-09-15 18:13:31 +00:00
Guardfile merging websocket-gateway into websocket-gateway 2013-09-15 18:07:00 +00:00
README.md merging websocket-gateway into websocket-gateway 2013-09-15 18:07:00 +00:00
Rakefile merging websocket-gateway into websocket-gateway 2013-09-15 18:07:00 +00:00
build * VRFS-438; collapsing all repos into one; requires modification of build files 2013-09-15 18:13:31 +00:00
jam_websockets.gemspec merging websocket-gateway into websocket-gateway 2013-09-15 18:07:00 +00:00
jenkins merging websocket-gateway into websocket-gateway 2013-09-15 18:07:00 +00:00
migrate.sh merging websocket-gateway into websocket-gateway 2013-09-15 18:07:00 +00:00

README.md

TODO & DESIGN LIMITATIONS

  • !!!! lock up multi-threaded unsafe data structures

  • The rabbitmq connection isn't pooled. Throughput limitation (but could be resolved by just starting more instances of JamWebsocket behind Haproxy)

  • The database connection isn't pooled. Throughput limitation (but could be resolved by just starting more instances of JamWebsocket behind Haproxy)

  • We make just one user topic registration and session registration for all users/sessions. If ever we had 10 of servers, it could be wasteful. It just depends on how fast the bogus messaging can be ignored

  • The database connection is pooled.

  • The user model is stored in memory, meaning periodically it should be reloaded from the database (in case a user was marked inactive and you want them knocked out of the system)

  • The user could easily join to multiple sessions. Currently, though, the ClientContext object only tracks one jam session topic subscription. This is minimial to change.

  • peek logic not implemented on server for protoc messages; this could be done to save cost of deserialization and serialization for session/user directed messages