Good Morning, On 6/Dec/2010, at 5:09 AM, Patrick Middleton wrote: > If an instance receives a request via a direct action and I don't want it to > be redirected via the load balancer, enough information is broadcast such > that other instances waiting for requests will be able to tell that another > instance should already be processing it, 'Should' is a strong word here. I don't think that I'd be relying on in. Perhaps I'm pessimistic?
> and then generate a response (without blocking on database i/o) to the effect > that database congestion may be in progress, that their request is being > processed, any database updates may or may not be committed but will be > committed at most once. Given that you've put rather bluntly that long request configuration won't work for you, I'm not sure how you expect to achieve this across multiple instances without building the infrastructure yourself. On 6/Dec/2010, at 7:06 AM, Patrick Middleton wrote: > What I am doing is reporting a bug in the WebObjects API adaptor, with the > circumstances as how how I encountered it. It might be possible to deduce, > for example, that the application list etc (see config.c in the Adaptors > project) is in shared memory, while uniqueID_counter (see transaction.c) is > not in shared memory, but should be, if we cared. > Anybody reading this list who is interested in the adaptor? Patches welcome! M. _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
