Hi MichaelThanks for the below.1. Would it be possible to contribute this feature or is there a reason to not have it going forward?2. Is it possible to disable the other threads and just have the listener? Smaller devices that don't have as many cores really struggle with multithreaded applications and if there are already threads in an application it may add additional overhead and complexityThanks & RegardsAshton Original Message Subject: Re: com.sun.httpserverFrom: Michael McMahon To: ashtonho...@ymail.comCC: net-dev@openjdk.java.netHi AshtonOn 28/03/2017, 12:26, ashtonho...@ymail.com wrote:> Hi all>> I was looking through the archives but did not find any answers to these questions so I figured I'd try here, hopefully this helps someone else as well.>> I've done some testing on the httpserver and come across some things:>> 1. No support for websockets (ws) or secure websockets (wss) - will this be in a future release?There are no plans at present to add support for websockets to this implementation.> 2. When starting the server a number of threads are spawned regardless of whether you specify an executor or not. Was this the intention? If so then why does it spawn multiple threads when it could just spawn one for listening that places all HttpExchange instances into a BlockingQueue or something for the developer to use in a single or multithreaded environment?Yes, just looking at the implementation, there are 2-3 threads created. One thread is the listener for incoming connections,plus one or two more for operating timer functionality. The executor is only used for handling incoming requests.Regards,Michael.> Thanks& Regards> Ashton
