[Info-vax] Integrity iLO Configuration?

[Arne Vajhøj]

On 6/25/2021 9:12 AM, Dave Froble wrote:
> On 6/25/2021 4:48 AM, Jan-Erik Söderholm wrote:
>> Den 2021-06-25 kl. 00:38, skrev Dave Froble:
>>> I need to develop a better method of handling lots of socket connect
>>> requests.  I also need to see if my ideas will work Ok.
>>
>> How many are "lots of"?
> 
> That is sort of undefined at this time.  Historically, the usage has 
> continued to rise.  Not sure what it could rise to.  So far we've seen 
> maybe 20K per hour at times.

20K per hour is 333 per minute or 5.5 per second.

That should be manageable.

100 ms sessions => 1 worker
1 s sessions => 10 workers
10 s sessions => 100 workers

>>> 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?
> 
> Clients use a protocol we've designed and implemented.  The source of 
> connection requests doesn't matter.  Some are from VMS, others from 
> various types of clients.
> 
>> 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.
> 
> No, WASD will not satisfy our requirements.  It's not just accepting 
> connections.  It is very specific apps that handle the requests.  One of 
> the requirements is identifying the incoming request as valid as early 
> as possible.  Failure at this point will immediately terminate the 
> connection.
> 
> WASD is  a "jack of all trades" type of app, and does that reasonably 
> well.  What we require is a specialist, for various reasons.

> One size does not fit all.

95% is HTTP today, but that leaves 5% for everything else.

Non-HTTP approaches are still seen.

If you have a requirement to be easily accessible from multiple
languages then then you could look at Thrift.

I still believe that a multi-threaded listener doing IPC with
workers is the right design.

The workers can be VMS Basic.

But you will need something else for the listener.

>                                For our customers, it seems that 
> internet communications is replacing most of the previous activity.

This internet thing seems to be staying around.

:-) :-) :-)

Arne