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 9b18849544 * working on feature ftue 2014-05-29 14:31:01 -05:00
..
bin * more websocket/heartbeat fixes 2014-04-30 03:01:28 +00:00
config * fixing tests for: * VRFS-1663 (diagnostics), VRFS-1657 (configurable timer for heartbeats), VRFS-1653 (websocket connection cleanup) 2014-05-01 14:09:33 -05:00
features merging websocket-gateway into websocket-gateway 2013-09-15 18:07:00 +00:00
lib * working on feature ftue 2014-05-29 14:31:01 -05:00
log merging websocket-gateway into websocket-gateway 2013-09-15 18:07:00 +00:00
script/package * deal with chuid differently so pre-script works 2014-02-05 02:13:41 +00:00
spec * merging develop into feature/scheduled_sessions 2014-05-07 15:04:41 -05:00
.gitignore * VRFS-438 - squirt out BUILD_NUMBER into file and make debian packages reference it when it starts the app so that gem versions can be found 2013-09-16 17:03:26 +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 fix warning related to ruby- prefix in .ruby-version files 2013-12-27 16:28:28 -05:00
.simplecov * VRFS-1103 - coverage for all projects. need to figure out how to merge all 2014-02-13 22:11:30 -06:00
Gemfile VRFS-1705 - 'monitor' subproj initial commit 2014-05-21 16:52:11 -05: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 * intsall to vendor/bundle 2014-02-02 14:03:31 -06:00
jam_websockets.gemspec merging websocket-gateway into websocket-gateway 2013-09-15 18:07:00 +00:00
jenkins * VRFS-1016 2014-01-31 14:25:17 -06: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