>domain  (obviously). This is fine for simple authentication tasks such
>as   necessary  for  POP3/SMTP,  and  even  some  of  Web  Messaging's
>functionality.  But  the  moment users manage certain account settings
>using  the  normal  WM  interface,  the setting will be changed in the
>Registry  and will not be propagated back to the database. Presto--the
>connection  is  broken. And hooking the Registry API is not within the
>realm of reason, trust me.

Well, I don't have to trust you.  The master database has to be exclusively 
on SQL database, any other products like Imail that need data from, or need 
duplciate data from, will get synced to that, trying to sync in both 
directions is crazy.

>There  are  two  possible solutions. First is to remove the links from
>Web  Messaging  for any setting that would get stored in the registry,
>and  build  an  "advanced  management  interface" in ASP/Perl for such
>settings  that  goes through the back-end DB first to ensure two-phase
>commit.

yes.

>Your  idea  does have significant technical hurdles as well

I didn't say it would be easy, but there has to be a central "customer 
database" on SQL as the foundation, master database, and other apps get the 
bits they need from there.  Simply because SQL is a better general purpose 
database technology than a registry database.

> >Clearly, this the only way to scale Imail seriously.
>
>It  is *a* way, but it is certainly not the only way. There are plenty
>of  things  that  Ipswitch could do to improve the efficiency of their
>SQL  calls--like  I've  said  so  many times, using the native SQL API
>(OLEDB)  rather  than  a  flatly  outdated  DSN-ful  ODBC call will be
>significantly   faster;   removing   the   reliance  on  the  external
>ODBCUSER.DLL  (by  embedding  the  logic  right  in the code for basic
>connectivity)  would  also  be  better.

that still splits the database between some it on Ipswitch/registry and 
other bits on SQL.

>think it's necessary for the application to treat DBAs with kid gloves
>regarding  performance  tuning  (though it would be much better if the
>docs  even  mentioned  such things).

I really can't imagine running 200k users out of the registry as a 
database.  (I remember at one point that MS admitting NT4 SAM pooped out at 
14K users.)

Len



Please visit http://www.ipswitch.com/support/mailing-lists.html 
to be removed from this list.

An Archive of this list is available at:
http://www.mail-archive.com/imail_forum%40list.ipswitch.com/

Please visit the Knowledge Base for answers to frequently asked
questions:  http://www.ipswitch.com/support/IMail/

Reply via email to