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
Nuwan 861722e5d4 includes fixes in profile edit form and lobby page 2024-02-12 19:11:11 +05:30
..
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 includes fixes in profile edit form and lobby page 2024-02-12 19:11:11 +05:30
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 change database migrations to be natural rails db migrations. 2021-02-13 20:17:18 -06:00
.gitignore wip - react components related to musician listing and filtering 2021-10-13 22:51:30 +05:30
.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
.simplecov * VRFS-1103 - coverage for all projects. need to figure out how to merge all 2014-02-13 22:11:30 -06:00
Gemfile Gemfile changes for moden computers 2021-05-22 15:24:00 +05:30
Gemfile.alt for modern O/S setup use Gemfile.alt instead of default Gemfile 2021-05-22 15:24:00 +05:30
Gemfile.lock wip sepcs for musician latency badge 2021-05-29 14:38:34 +05:30
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 change database migrations to be natural rails db migrations. 2021-02-13 20:17:18 -06:00
build more debugging 2021-04-02 17:05:48 -05: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