| Re: [jetty-users] Jetty 7 upgrade issue |
|
Greg,
I can potentially work on this because I need it. I am in the middle of converting all of my other code at the moment so I want to get that work done first and will probably save this for last. It could be a week or two before I start looking at it. In case someone can tackle this before I can... In Jetty 5, I have my own HttpTunnel class because I occasionally need to check some security things as data is moving through the tunnel and potentially disconnect the connection. It would be nice if the ConnectConnection had something like a filter that I could register that would do my specific checks and indicate if the connection could be dropped. That saves me the extra (duplicated) work of building my own tunnel to just add the small piece of code I need. Also, the one thing that is bad about the way this works in Jetty 5 is the fact that I tie up a listener thread when a client is connected plus I have another thread going that copies data back to the client. Obviously this doesn't scale so it would be nice (required?) if this was totally asynchronous. Not to pile on about documentation but, since the javadocs are slim, it could take me a while to figure this out so I am all for a Jetty expert tackling it :) Tony Greg Wilkins wrote: Tony, I've had a quick look and it should be pretty simple to write. You need to create a ConnectConnection that is really just a simplification of WebSocketConnection. Instead of a parser/generator it will just have the buffers and will copy data through. You can set this up more or less the same as websocket, but you need to send a 200 response first and then set the response status to 101. The advantage of this approach is that it will be asynchronous and will not need threads.... well you might use 1 thread to handle the outbound connection, if you don't want to do an async handler for that. Do you think you will have a go at implementing this? cheers Greg Wilkins wrote: This message (and any associated files) is intended only for the
use of the individual or entity to which it is addressed and may contain information that is confidential, subject to copyright or constitutes a trade secret. If you are not the intended recipient you are hereby notified that any dissemination, copying or distribution of this message, or files associated with this message, is strictly prohibited. If you have received this message in error, please notify us immediately by replying to the message and deleting it from your computer. Messages sent to and from Stoneware, Inc. may be monitored. |