Good Morning, On 15/Nov/2010, at 8:43 AM, Greg Lappen wrote: > #1 - Only one thread can be processing at once. I seem to recall that this > is a limit in EnterpriseObjects but it's been a while. Well, yes, t's hard for a single thread to process more then one thing at a time. ;-) Test your app with concurrent request handling turned on and then release it to the wild! (Yes, I have thought that you might have meant one database transaction at a time however you didn't say that.)
> #2 - EnterpriseObjects caches every object from the database. An awfully general statement. This does not have to be the case if you don't want it to be. > With that being said, how can you horizontally scale your application layer? Add more instances. > If you setup more instances of your app, they each have their own caches, > which will be out of sync with each other. Why? Optimistic locking if that makes sense for your app handles this just fine. Otherwise pessimistic locking works as long as your database back end supports it. Setting the EOF lay appropriately will let you handle stale data with minimal work and there are more intricate ways to sync across instances if that's really what you need. > Is there a commonly used framework for doing distributed cache management? Sure, however does your application really need this? The EOF layer already handles freshness automatically and so you might not need to do anything. Again, highly application specific. > And is it possible to make your applications multithreaded so page requests > can be processed concurrently? Yes. M. _______________________________________________ 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
