immutant

http://immutant.org Note: dev discussion happens in #immutant on FreeNode IRC.
2015-09-23T00:37:49.000075Z

@michal: I haven't seen that specific error before, but that can be caused when there is a class on the classpath that is a duplicate of one in the proper jar

2015-09-23T00:37:56.000076Z

can you gist your project.clj?

2015-09-23T00:38:11.000077Z

or the output of lein deps :tree?

michal 2015-09-23T08:26:01.000078Z

@tcrawley: yup, that was the case. ring-middleware-format is pulling ring/ring-jetty-adapter dependency which in turn pulls javax.servlet/servlet-api. simple exclusion made made it working again. thanks!

2015-09-23T12:51:14.000079Z

@michal: glad you figured it out

colin.yates 2015-09-23T16:11:36.000081Z

hi all - anyway to get run-dmc to not open a browser window?

2015-09-23T17:28:02.000082Z

@colin.yates: I just replied on twitter. with-redefs is probably your best bet right now

2015-09-23T17:28:14.000083Z

or altering the var root of browse-url

colin.yates 2015-09-23T17:32:48.000084Z

Thanks @tcrawley - issue raised: https://issues.jboss.org/browse/IMMUTANT-582

2015-09-23T17:33:02.000085Z

thanks :)

colin.yates 2015-09-23T17:34:03.000086Z

for web sockets, the doc states msg is either a String or byte[] - if I am using transit-cljs then it seems to come through as a String - this seems inefficient. Is there a way to hook into the byte-array before it is converted to a String?

2015-09-23T17:35:54.000087Z

that would make me think that client-side is sending a TextMessage instead of a BytesMessage, so it would already be a String by the time we get it. Seems like you would have to change that on the client side

colin.yates 2015-09-23T17:37:37.000088Z

ah OK - I am using goog…WebSocket so will look there

2015-09-23T17:38:04.000089Z

does js even support byte arrays? I'm not very cluefull there

colin.yates 2015-09-23T17:38:21.000090Z

no idea - I assumed it did, but you know what they say about assumptions :simple_smile:

2015-09-23T17:38:44.000091Z

:)

colin.yates 2015-09-23T17:39:20.000092Z

yeah, so http://closure-library.googlecode.com/git-history/docs/class_goog_net_WebSocket.html states .send takes in a String.

2015-09-23T17:39:23.000093Z

basically, you'll only get a byte[] if the incoming message is a BytesMessage (in case I wasn't clear enough)

colin.yates 2015-09-23T17:39:35.000095Z

you were - thanks.

2015-09-23T17:39:49.000096Z

ah, so String it is

2015-09-23T17:40:06.000097Z

I'm sure that's a byte[] at some low-level in undertow, but we can't get at it

colin.yates 2015-09-23T17:41:27.000098Z

I fully expect any performance gains are all noise anyway for this, and probably most web applications. Thought I would ask simply so I don’t need to decide on a String encoding when I call .getBytes when I turn it back into a byte array for the transit reader.

colin.yates 2015-09-23T17:41:36.000099Z

I am a bad, bad developer today :simple_smile:

2015-09-23T17:41:43.000100Z

heh