Avoiding session creation for DirectActions
Avoiding session creation for DirectActions
- Subject: Avoiding session creation for DirectActions
- From: Musall Maik <email@hidden>
- Date: Tue, 31 May 2016 17:35:26 +0200
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