Hi all,
Currently, as far as I understand, HiveMind's Pooled ServiceModel does not
offer all benefits of a "real" pool in the sense that its size is unlimited
and unconfigurable (for the "initial size"), in addition it never shrinks
after a heavy-load, so even after load has gone back to normal, unnecessary
resources (pooled services) are still in memory.
I was wondering if there are some possibilities to enhance this ServiceModel
(or create a new one) that could implement those features as parameters
settings (for each service):
- initial size
- maximum size
- wait or fail if exhausted resources (with timeout?)
-...others?
Plus the definition of default values (to avoid configuration for all pooled
services).
I also wonder if this could be achieved easily (from the HiveMind internal
changes development viewpoint).
One idea that I had about configuration was to use the kind of parameter
settings as for the "translator", ie model="pooled,min=10,max=20...", this
way, there would be no changes in HiveMind schemas definitions.
I would have liked to dig into HiveMind "guts", but to be honest, I find it
hard to understand how the ServiceModels interact with the
ServiceImplementationFactories. Maybe some documentation (like activity
diagrams) would be useful for all of us who would like to take part into
HiveMind improvements?
Do other people in this list think such a kind of pooled model would be
worth?
Cheers
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
