Switching WebSocket Write Mode at Runtime

[bbarrington42]

Please expose a configuration setting so that the websocket write mode can be set at runtime. Currently, I am setting it via and initialization parameter in my web.xml. But there is no way to change it after startup.

Thanks,
Bill

(previously discussed via email with jfarcand and requested by him to submit this as an issue) :-)

[jfarcand]

OK at least you can switch at deployment time using

<param-value>org.atmosphere.websocket.binaryWrite</param-value>
<param-value>true</param-value> 

[bbarrington42]

Hello,
Just curious as to whether or not you've had any time to look into this.

Best regards,
Bill

[jfarcand]

Salut, probably next week I will. The API is there, it just need to be properly exposed.

[bbarrington42]

Awesome. Thank you very much.

-Bill

On Thu, Jan 31, 2013 at 8:25 AM, Jeanfrancois Arcand <
[email protected]> wrote:

Salut, probably next week I will. The API is there, it just need to be
properly exposed.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/857#issuecomment-12942010.

[bbarrington42]

Along the same lines as this, would it be possible to maintain some connections using binary write mode and other connections using text write mode all negotiated at runtime? Looks like we could have a need for this in the future based on an existing client. Just wanted to get an update on where this effort is. Thanks very much.

[jfarcand]

@bbarrington42 As you might have read (wil make an official announcement this week), I'm starting my own company around Atmosphere. I will continue supporting the community like I do, but I will prioritize features asked by paying/support customers. So expect a little delay...but I will do it this year, before 1.1 for sure. Thanks!

[jfarcand]

If all goes well, I should have it working by tomorrow.

[jfarcand]

OK I won't fix that as most of the container/server doesn't supports it, specially jsr 356.