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 8393506f52 connection policy 2020-12-18 17:22:12 -06:00
..
bin * upgrade to Rails 4 as well as support JjamBlaster 2016-07-17 10:16:27 -05:00
config lots of progress on amazon-readiness 2017-07-09 21:21:29 -05:00
features merging websocket-gateway into websocket-gateway 2013-09-15 18:07:00 +00:00
lib connection policy 2020-12-18 17:22:12 -06:00
log merging websocket-gateway into websocket-gateway 2013-09-15 18:07:00 +00:00
script/package * websocket-gateway GATEWAY_NAME fixes 2014-09-25 20:40:31 -05:00
spec invite actually working 2020-04-04 17:51:36 -05:00
.gitignore use Gemfile.lock 2017-12-17 20:26:20 -06: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 feed fix 2020-04-21 09:04:30 -05:00
Gemfile.lock expand chat window link 2020-04-22 11:40:54 -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 merge conflict from feature/new_session (VRFS-3283) 2015-07-15 10:04:45 -05: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