seth
/
jam-cloud
mirror of https://bitbucket.org/jamkazam/jam-cloud.git
1
0
Fork 0
Code Issues Actions Packages Projects Releases Wiki Activity
88 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 11458f0d39 * updating pg_migrate to 0.1.7 to match the rest of the site 2013-05-18 06:50:39 -05:00
bin * fixing startup of websocket-gatceway 2013-03-14 23:54:20 -05:00
config renamed connection timers to correspond to state names 2013-02-11 00:04:41 -06: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 * updating pg_migrate to 0.1.7 to match the rest of the site 2013-05-18 06:50:39 -05:00
log * VRFS-190; gitignore/remove accidentally added log files 2013-01-05 02:40:05 -06:00
script/package * -f so no error if not present 2013-01-16 22:51:04 -06:00
spec * VRFS-259: beta signup 2013-03-14 23:24:25 -05:00
.gitignore * VRFS-190; gitignore/remove accidentally added log files 2013-01-05 02:40:05 -06:00
.pg_migrate * websocket gateway allows login to server and to session 2012-08-23 21:46:58 -05:00
.rvmrc * p327 set as defaul 2012-12-06 06:45:52 -06:00
Gemfile * updating pg_migrate to 0.1.7 to match the rest of the site 2013-05-18 06:50:39 -05: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 * remove vendor/bundle 2013-01-14 00:03:46 -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 * deb server 2013-01-05 23:18:26 -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