Jim Jagielski wrote:
I think the whole issue revolves around whether the balancer
should, or should not, pre-open connections and manage them
internally, or whether it should be one-shot. The real
power is being able to load balance, and implement
that in a central location.
So it seems to me that some sort of Balancer member
option that determines whether or not the connection
is "persistent" or not would alleviate some of
the issues you raise.
That would be the ideal model for any remoted ASP.NET container as well.
Some persistance flag to indicate that a backed should be persistant,
and pooled, and the pool constraints (for this client side, not the actual
backend's true constraints), would be ideal.
Bill
