• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Instance ID wrong?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Instance ID wrong?


  • Subject: Re: Instance ID wrong?
  • From: Patrick Middleton <email@hidden>
  • Date: Tue, 2 Dec 2008 11:09:40 +0000


On 2 Dec 2008, at 10:47, Andrew Lindesay wrote:

Hello Anjo;

Yes this can be quite annoying -- the user gets a session timeout. I guess the problem is that beyond the instance number in the path, the adaptor doesn't know there is or is not a session.

cheers.

before proceeding. Now, the problem is that there may several reasons for 20 not to reply, but now instance 10 has no way of knowing that the session that doesn't exist in it's own session store didn't really expire but comes from a temporarily unavailable instance 20. Does anyone have enough inisght into the adaptors to say why the request is rewritten? It looks pretty dumb to me, but maybe there is a good reason... I think if should store the old request add at least a header to indicate that this is not the intended instance.

___ Andrew Lindesay www.lindesay.co.nz

I too have encountered the problem where a stateful request is redirected to a different instance because the requested instance did not respond, and I would strongly welcome an HTTP header or headers being added to indicate to instance the instances which have already not responded to this request.


The requested instance (or instances) usually doesn't respond because it's doing a very big database fetch; enabling concurrent request handling usually won't help much as other sessions will likely block waiting for access to the database. lifeabeat interaction with wotaskd should continue unimpeded.

How would an instance receiving a stateful request whose URL indicates it should be sent to a different instance make use of some X-WOInstanceDidNotRespond header then? How would the instance know whether the other instance(s) are busy but not dysfunctional, have hung, or have crashed?

If we really wanted to sort this out, we might be looking at persistent session state shared over all instances, so that any instance could respond to any request, whether stateless or stateful. I would not welcome being asked to implement that myself.

---
Regards Patrick
OneStep Solutions Plc
www.onestep.co.uk

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Follow-Ups:
    • Re: Instance ID wrong?
      • From: Anjo Krank <email@hidden>
References: 
 >Instance ID wrong? (From: Anjo Krank <email@hidden>)
 >Re: Instance ID wrong? (From: Andrew Lindesay <email@hidden>)

  • Prev by Date: Re: Instance ID wrong?
  • Next by Date: Re: Embedding D2W components in non-D2W applications
  • Previous by thread: Re: Instance ID wrong?
  • Next by thread: Re: Instance ID wrong?
  • Index(es):
    • Date
    • Thread