seth
/
jam-cloud
mirror of https://bitbucket.org/jamkazam/jam-cloud.git
1
0
Fork 0
Code Issues Actions Packages Projects Releases Wiki Activity
43 Commits 118 Branches 1,306 Tags 359 MiB
Ruby 37.9%
JavaScript 31.8%
CoffeeScript 11%
HTML 6.6%
SCSS 5.7%
Other 6.8%
Go to file
Seth Call 989544bb35 * fixing broken test in rspec 2012-12-03 22:08:17 -06:00
bin * ConnectionManager integrated 2012-10-23 06:42:28 -05:00
config * ConnectionManager integrated 2012-10-23 06:42:28 -05:00
features * initial commit of websocket gateway. login working, still working on login to jam session 2012-08-16 22:22:31 -05:00
lib Fixing a bug after MusicSessionClient was renamed to Connection. 2012-10-28 17:24:16 -07:00
spec * fixing broken test in rspec 2012-12-03 22:08:17 -06:00
.gitignore * initial commit of websocket gateway. login working, still working on login to jam session 2012-08-16 22:22:31 -05:00
.pg_migrate * websocket gateway allows login to server and to session 2012-08-23 21:46:58 -05:00
.rvmrc * midway through jruby>ruby port for VRFS-18 2012-10-22 19:58:57 -05:00
Gemfile * websocket-gateway build added 2012-11-18 02:08:33 -06:00
Guardfile * initial commit of websocket gateway. login working, still working on login to jam session 2012-08-16 22:22:31 -05:00
README.md * login and login_jam_session working with tests. logging cleaned up 2012-08-26 13:42:22 -05:00
Rakefile * initial commit of websocket gateway. login working, still working on login to jam session 2012-08-16 22:22:31 -05:00
build * websocket-gateway build added 2012-11-18 02:08:33 -06:00
jam_websockets.gemspec * initial commit of websocket gateway. login working, still working on login to jam session 2012-08-16 22:22:31 -05:00
jenkins * websocket-gateway build added 2012-11-18 02:08:33 -06:00
migrate.sh * websocket gateway allows login to server and to session 2012-08-23 21:46:58 -05: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