Does the ERXEC autolocking mechanism work in a non WO application? I.e. An EOF based application without the WO request/response loop? If not would we be able to create our own request response loop and hook in the ERXEC autolocking mechanism into it? Our thought was to do something at the thread level.
We created a custom JSP tag library that uses EOF but not WO. It has been running for the past few years but we just moved to Project Wonder and we noticed that it is pretty slow. The tags are read only and there can be >20 per JSP page. The tags are essentially stateless and unaware of each other. This is why we were using the EOSharedEditingContext. Spawning a new EOEditingContext per tag really killed our performance. The SharedEditingContext greatly reduced the database thrashing. Thanks in advance for any thoughts? Dov Rosenberg
_______________________________________________ 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: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
