The websocket classes are in the Maven group org.eclipse.jetty.websocket.
https://search.maven.org/search?q=g:org.eclipse.jetty.websocket
On Sun, May 24, 2020 at 12:23 PM Johan Van Noten wrote:
> My intent:
>
> I have an existing Eclipse RCP application.
>
> I would like to interact with it
Matt,
if it is a file server, then you should do it asynchronously totally
asynchronously with async IO. That way threads are not a problem and the
fair share algorithms already built into TCP/IP and the OS will do all the
work for you.
So you startAsync, register a WriteListener and then
Hi Greg
Thank you very much for your suggestions, they're really useful.
Yes - I was thinking that we need to limit the total number of threads, as each
of them can use a lot of memory. I guess we could increase the thread pool size
to something large, and put a fair semaphore around the
Matt,
Are you doing this to try to limit the total threads, or just to make sure
that some threads are not starving others? If you don't mind the total
number of threads, then you could simply put in a Thread.yield() call every
50ms and not worry about async servlet handling.
Note also, from a
Hi
I was wondering if anyone could confirm whether what we've done is sensible -
it seems to work, but I'm not really confident and would like to know how
righteous it is!
Our HTTP server processes requests that can take minutes at a time, the
handling for which can easily be broken down into
