Re: Avoiding session creation for DirectActions
Re: Avoiding session creation for DirectActions
- Subject: Re: Avoiding session creation for DirectActions
- From: Michael Kondratov <email@hidden>
- Date: Tue, 31 May 2016 11:36:31 -0400
Maik,
Why not use stateless components and avoid session creation all together?
Michael Kondratov
Aspire Auctions, Inc.
216-231-5515
> On May 31, 2016, at 11:35 AM, Musall Maik <email@hidden> wrote:
>
> Hi all,
>
> in an application that gets frequent DirectAction calls from other applications, I'd like to reduce the overhead of creating a new session for every request. Currently I'm setting a short timeout, but creating and removing all those sessions seems like avoidable overhead.
>
> How about overriding WOApplication.createSessionForRequest()? I could try to determine if it was called from within DA processing, and then return a pooled session, but as I see it I'd have to fiddle with the _activeSessionsCount to compensate, and I suspect the rest of WOApplication always expects this method to return a newly created session.
>
> So, does anyone else do something similar?
>
> Thanks
> Maik
>
>
> _______________________________________________
> 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
_______________________________________________
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