RE: ODBC from IFS

["Joe Pluta" <joepluta@xxxxxxxxxxxxxxxxx>]

> From: Metz, Zak
>
> I would like to design a relatively generic model for a data
> queue-driven, dynamically scaling subsystem.
>
> Has anyone developed a generic design for such a thing. I'm thinking it
> would be controlled by parms such as minimum/maximum number of jobs, min
> delay before additional job started, min depth before additional job
> started, how often to check...but if someone has already gone through
> this exercise perhaps they would consider sharing what a flexible set of
> controlling parameters consists of, and any other gotchas?

I don't know about a generic design.  Each time I've implemented this there
have been different issues such as security, performance, auditing,
flexibility, and so on.

The most important thing is to develop a flexible, extensible message
format.  One that can handle all manner of requests, from small, simple
queries to large, multi-record transactions.


> And is there a shorter term for this sort of thing besides "data
> queue-driven, dynamically scaling subsystem?"

"Dispatcher", or a little more completely "Request Dispatcher".