From: Andrew N. <and...@vi...> - 2007-11-09 16:28:13
|
> > The more I think about this, the more I tend to think the current > design might be best left alone (at least, for now). Even if I were > able to lessen the number of network connections to Voyager (getStatus > calls), if Voyager is slow to respond, we are still most likely to end > up with the same result: a frozen application. In the end, I would > just be "buying a little time" before the inevitable occurs: maxing > out the allowable limit of network connections. > > In any case, I still think this topic is somewhat important. If > nothing else, one might recognize this symptom when a user complains > about it. Also, later on, as we gain more experience in a production > environment (heavy load), we might find that we can achieve better > responsiveness if we called getStatus, say, 4 or 8 items at a time > instead of one-by-one. Just thinking out load... > Yeah, I agree. I think this is something that needs to be reevaluated post= production. Andrew |