> Server request per msg per user. Is not necessary. Sure it is. This is the only way to allow the back end to be updated asynchronously, whether through the GUI, web administration, ODBC, or whatever.
> But a separate service is idea Sure, but your app is not a cache. It's a middle tier that uses a two-phase commit, and you've implemented it in a situation where all transactions go through this tier. Imail will still, as it should, check the Registry (which runs from RAM) on every message. I am very happy that it does, rather than having to, say, restart all the services whenever you add a user asynchronously to refill the cache. And I'm happy that we don't have to run anything on the Imail server to reread the whole back end into a separate memory cache (true, this would be useful for some people, but would be ridiculous under load and a big user base). If you want to have a distributed system, these are the costs. Sandy ______________________________________________________________________ The HKSI-IMail Admin List is hosted by........ Humankind Systems, Inc. Questions, Comments or Complain like Hell.. mailto:[EMAIL PROTECTED] Message Archive... http://www.tallylist.com/archives/index.cfm/mlist.4 To Manage your Subscription......... http://humankindsystems.com/lists
