[Info-vax] Integrity iLO Configuration?
Arne Vajhøj
arne at vajhoej.dk
Fri Jun 25 08:44:58 EDT 2021
On 6/25/2021 4:48 AM, Jan-Erik Söderholm wrote:
> Den 2021-06-25 kl. 00:38, skrev Dave Froble:
>> Current thoughts are a single listener that validates requests,
>> accepts the connection, and passes it off to a worker process, then
>> drops it's own connection to the socket. Involves some inter-process
>> communications. Listener might get rather busy, but will spend little
>> time on each request.
>
> How are the clients deigned? Calls from Javascript running in browsers?
> Are the clients your own applications too?
>
> For the usual HTTP (and everything related to that) based communication
> WASD will provide most of what you need out of the box. Have you yet
> looked at WASD? What you describe as your "current thoughts" above
> is just a description of how WASD works.
A standard web server is great if the protocol is HTTP.
For something custom TCP not so much. And from last time this
came up I think David is on custom TCP communication.
If HTTP and web server then the choice is between a general purpose
web server or something designed for being embedded in the application.
If general purpose web server then WASD is one of the
possibilities.
Arne
More information about the Info-vax
mailing list