We sort of solved this problem by storing long running tasks in Application class.
Michael Kondratov Aspire Auctions, Inc. 216-231-5515 > On May 29, 2018, at 6:02 AM, Mark Wardle <m...@wardle.org> wrote: > > Thanks Samuel. Perhaps I should do this purely in the browser in JS and hit a > REST endpoint and then pass a ticket to a WO DA when I know credentials are > correct. > > Mark > > On Thu, 24 May 2018 at 22:39 Samuel Pelletier <sam...@samkar.com > <mailto:sam...@samkar.com>> wrote: > Hi Mark, > > I've never done that with WO but it is possible to return partial data to the > browser and have it rendered bi using chunked response. I do not know if it > is possible to force WO to flush the response content to the client and keep > adding content after... > > If you can validate that the request is from a human and look valid, you may > defer the session creation after this validation and have a quick response > for failure. > > Otherwise, just create session with very short lifespan like 5 minutes with > setTimeOut(5*60) in the session constructor and adjust it after the > successful logon with WOSessiion.setTimeOut(3*3600); // for 3 hours > > I now tend to add an AjaxPing to my wrapper and use shorter session. > > Regards, > > Samuel > > > > Le 24 mai 2018 à 17:18, Mark Wardle <m...@wardle.org > > <mailto:m...@wardle.org>> a écrit : > > > > Hi all, > > > > I am cleaning up some code and identifying some long-acting responses that > > sometimes take 2-3 seconds because they call external services over a > > network. I'd like to turn them into long responses to show users that > > something is happening and also prevent alerts in my log files. One of the > > sometimes slow actions is logging in via a KDC. > > > > I have found ERXLongResponse which looks as if it will do the trick but it > > is unclear to me whether this will work for user login. My landing page > > using exclusively direct actions to prevent inadvertent session creation. > > Is there a way of running a long response task without creating a session? > > > > Many thanks, > > > > Mark > > > > _______________________________________________ > > Do not post admin requests to the list. They will be ignored. > > Webobjects-dev mailing list (Webobjects-dev@lists.apple.com > > <mailto:Webobjects-dev@lists.apple.com>) > > Help/Unsubscribe/Update your Subscription: > > https://lists.apple.com/mailman/options/webobjects-dev/samuel%40samkar.com > > <https://lists.apple.com/mailman/options/webobjects-dev/samuel%40samkar.com> > > > > This email sent to sam...@samkar.com <mailto:sam...@samkar.com> > > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/webobjects-dev/michael%40aspireauctions.com > > This email sent to mich...@aspireauctions.com
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
