search

jarohen / chord

A library designed to bridge the gap between the triad of CLJ/CLJS, web-sockets and core.async.
439 stars 40 forks source link

Messages appear on server as TaggedObject rather than clojure value. #47

Open retrogradeorbit opened 8 years ago

retrogradeorbit commented 8 years ago

Hi there again!

So after getting fressian transport working, what I've found is when you send a message from the server to the client, the message appears on the client close to what was sent (a vector turns into a sequence), but when sending from the client to the server, instead of getting either, I seem to get an org.fressian.TaggedObject Object instead of a clj collection.

example project here: https://github.com/retrogradeorbit/multiplayer

After client connects it sends [:login :test] down the channel. On receipt, the server prints what it gets and the following appears:

message was org.fressian.TaggedObject@e272218

Note, this is embedded inside the hashmap response. Printing the whole message pulled from the channel:

{:message #object[org.fressian.TaggedObject 0x2f5285c "org.fressian.TaggedObject@2f5285c"]}
jarohen commented 8 years ago

Hey Crispin - thanks for reporting, will take a look. (Maybe @rosejn could give us a pointer, if he's around?)

Thanks,

James

rosejn commented 8 years ago

Hey,  This is due to bugs in fressian-cljs that we've fixed and issued a PR for recently.  Hopefully the author merges and issues a new release soon.

On Wed, Feb 17, 2016 at 12:39 AM -0800, "James Henderson" notifications@github.com wrote:

Hey Crispin - thanks for reporting, will take a look. (Maybe @rosejn could give us a pointer, if he's around?)

Thanks,

James

— Reply to this email directly or view it on GitHub.