• 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: WO Long Response and iPhone
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: WO Long Response and iPhone


  • Subject: Re: WO Long Response and iPhone
  • From: Chuck Hill <email@hidden>
  • Date: Fri, 15 Jan 2010 10:58:05 -0800


On Jan 15, 2010, at 12:21 AM, Andrew Lindesay wrote:

Hello Chuck;

Assuming an instance with concurrent request processing turned on, if there are a number of sessions (or even stateless users) on the same instance with a large volume of transactions, will the streaming WORequest multiplex with the other requests?

Not sure what you mean by "multiplex". I think it may use a WOWorkerThread for the duration of the upload, but I am not certain.



My understanding was that the WebObjects adaptor queues requests into an instance rather than multiplexes them.

Instances will accept request up to # of Worker Threads + Listen Queue Size. More than that, and the adaptor will return an error message. Worker Threads process in parallel, subject to single threaded locks in EOF.



So if a large transaction arrives from a slow pipe, will it not block the other requests until either the adaptor times it out or a response is returned to the client?

Not if concurrent request processing is on. It will block that one session and WOWorkerThread (again, I think).



PS: The javadoc for WORequests refers to the "wis" request handler -- I hadn't heard of this one before!

That is for direct actions.

Chuck



cheers.

Are you using the streaming handler for uploads? If you are, there should not be any timeouts from the adaptor. I've seen uploads of large files over slow connections to GVC.SiteMaker go on for a very, very long time with no timeout.
...
I wouldn't up the time on the adaptor because other clients who are using that instance will get blocked and may reach their timeouts.
...
In my case, I don't think upping the adaptor timeout will block since WOAllowsConcurrentRequestHandling is set to true. Does that sound correct?

___ Andrew Lindesay www.lindesay.co.nz


-- Chuck Hill Senior Consultant / VP Development

Practical WebObjects - for developers who want to increase their overall knowledge of WebObjects or who are trying to solve specific problems.
http://www.global-village.net/products/practical_webobjects








_______________________________________________
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


References: 
 >WO Long Response and iPhone (From: Joe Moreno <email@hidden>)
 >Re: WO Long Response and iPhone (From: Andrew Lindesay <email@hidden>)
 >Re: WO Long Response and iPhone (From: Joe Moreno <email@hidden>)
 >Re: WO Long Response and iPhone (From: Chuck Hill <email@hidden>)
 >Re: WO Long Response and iPhone (From: Andrew Lindesay <email@hidden>)

  • Prev by Date: Re: Modeling an optional to-one relationship
  • Next by Date: Re: WO Long Response and iPhone
  • Previous by thread: Re: WO Long Response and iPhone
  • Next by thread: Re: WO Long Response and iPhone
  • Index(es):
    • Date
    • Thread