server-spinach: pinging, registration, moves #5
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Pinging/ponging
* GCing
* Player registration
* Moving
Example (with ponging off):
*Client> forM_ [cmain, cmain, cmain] forkIO
*Client> + Sending {"email": "ThreadId 282"}
+ Sending {"player": {"email": "ThreadId 282"}, "x": 1.0, "y": 1.0}
+ Sending {"player": {"email": "ThreadId 282"}, "x": 0.0, "y": 0.0}
+ Sending {"email": "ThreadId 283"}
+ Sending {"player": {"email": "ThreadId 283"}, "x": 1.0, "y": 1.0}
+ Sending {"player": {"email": "ThreadId 283"}, "x": 0.0, "y": 0.0}
+ Sending {"email": "ThreadId 284"}
+ Sending {"player": {"email": "ThreadId 284"}, "x": 1.0, "y": 1.0}
+ Sending {"player": {"email": "ThreadId 284"}, "x": 0.0, "y": 0.0}
+ Pinged: "{\"ping\": true}"
+ Ponged
+ Pinged: "{\"ping\": true}"
+ Ponged
+ Pinged: "{\"ping\": true}"
+ Ponged
ghc: ConnectionClosed
ghc: ConnectionClosed
+ Pinged: "{\"ping\": true}"
+ Ponged
ghc: ConnectionClosed
+ Sending {"player": {"email": "ThreadId 283"}, "x": 0.5, "y": 0.5}
+ Sending {"player": {"email": "ThreadId 282"}, "x": 0.5, "y": 0.5}
+ Sending {"player": {"email": "ThreadId 283"}, "x": 0.7, "y": 0.7}
+ Sending {"player": {"email": "ThreadId 282"}, "x": 0.7, "y": 0.7}
+ Good night
+ Good night
+ Sending {"player": {"email": "ThreadId 284"}, "x": 0.5, "y": 0.5}
+ Sending {"player": {"email": "ThreadId 284"}, "x": 0.7, "y": 0.7}
+ Good night
hlian
force-pushed
the
server-spinach
branch
from
0ec46f0 to
54fadc2
Compare
|
i love it |
ianthehenry
added a commit
that referenced
this pull request
Sep 6, 2014
server-spinach: pinging, registration, moves
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is essentially Basilica's sockets with a few tricks from my sleeve:
runMaybeT . foreverinstead of a tail callwebsocketsis insensibly terrible 1 2 at handling exceptions, and the best way to work around it is to catch and finagle them ourselvesPlayerandMoveto be independent of the rest of the application, soConnectionobjects are directly stored in theDB. This allows for a slight simplification of the heartbeat, which becomes a fancyfilterMBecause GHCI doesn't fork to run main, you'll have to keep
kill $(lsof -i :9160 | tail -n 1 | tr -s ' ' | cut -d ' ' -s -f 2)-ing in order to make it let go of the port. I recorded a little Emacs macro withC-(andC-)to do it for me, but I think it's easier to just have iTerm open and usecabal run.I also had another tab open with
cabal replfor:load Client, cmain.