Hi Maik, Sounds like your application doesn't actually need sessions. I’d start by looking at where sessions are being created and then try to eliminate session creation altogether. Unless session() is explicitly invoked in your DAs or components, requests will generally not create new sessions.
- hugi > On 31. maí 2016, at 15:35, Musall Maik <m...@selbstdenker.ag> 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 (Webobjects-dev@lists.apple.com) > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/webobjects-dev/hugi%40karlmenn.is > > This email sent to h...@karlmenn.is _______________________________________________ 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
