On 12/2/2015 7:47 AM, Jay McCarthy wrote:
Hi George,
The output port (and input port) that a response gets is the real
port, meaning that it has a file-descriptor and can be shared across
places. I suggest having one serve/servlet place that does the
dispatching, forwards the port (perhaps
Hi George,
The output port (and input port) that a response gets is the real port,
meaning that it has a file-descriptor and can be shared across places. I
suggest having one serve/servlet place that does the dispatching, forwards
the port (perhaps using response/output if you know the headers
Hi all,
I'm not sure exactly how to phrase my questions, so let me give a bit of
background.
I have a fairly large (and growing) web middleware application that uses
serve/servlet and currently exposes about 90 function URLs, all of the
form "/api//". The application grew precipitously
You probably thought of this, but could you hand the ports themselves
over to the worker places after the dispatch but before any other
processing happened? Or maybe just make each place run the entire
server and then hand the ports over before dispatching and dispatch
inside each worker place?
4 matches
Mail list logo
