JMS support doesn't currently exist for Wink. Wink, to date, has been purely HTTP-based. I'm a little confused as to your motivation to go that way though. Is it to reduce chattiness (and number of outstanding number of connections) of clients/services? Or more to have clients submit longer running jobs and not leave connections idle?
> That and HTTP is pissing me off. Not much we can do about that one. ----- Original Message ---- From: Jason Dillon <[email protected]> To: [email protected] Sent: Tue, September 21, 2010 5:28:32 PM Subject: JMS Transport Just wondering if you guys know of anyone doing JAX-RS over JMS? Specifically, using JMS to establish the communication channel, then send/rx REST messages ver that channel (instead of making a new HTTP request each time). ATM my main users are a java client, though need to keep the window open for a web UI later and I'd like to keep using JAX-RS bits as the main entry point. Just that I would rather connect/secure the clients channel once and then overload it for passing async messages back via cometd-ishly as well. That and HTTP is pissing me off. Anyways, anyone know if this exists somewhere and if not how difficult it might be to implement a JMS transport for wink? --jason
