Hello Sanford,

Monday, November 8, 2004, 4:36:07 PM, you wrote:

>> They  are  so  far  ahead of Imail by using. . . XML instead of. . .
>> registry it's not funny.

SW> Hrm.  An  XML  file vs. a memory-mapped, intelligently cached, indexed
SW> b-tree.

The biggest problem with the registry is that it is basically an
opaque binary file structure that if (when) it gets corrupted is
almost irretrievable.

SW> Or an XML file vs. a central RDBMS already holding subscriber data and
SW> used by multiple third-party applications.

Sure, a full-fledged RDMS would be much more efficient and manageable.
Problem is, Imail ain't. Like right now, Imail doesn't know spit about
views or use any decent structure, so we have to trick it into
thinking the views it's seeing are tables. Problem is, updating a view
is mighty tricky. And trying to use Imail's 1 table per domain
structure is pure insanity; flying totally in the face of sound
database management and normalized data practices.

SW> Or an XML file vs. a distributed LDAP directory serving up a corporate
SW> userbase from RAM.

Yes, more efficient than XML but can/are all parameters stored in the
directory? No, just userbase which then must be matched to other
configuration parameters and managed separately.

SW> syncing to an RDBMS or other directory is not flexibility.

Web services make it extremely flexible, just not easy.

SW> The  recent  claims that IMail functionality is "behind the times" are
SW> provable  in  almost  every case, but completely fail when it comes to
SW> userbase  management.

Ever restored and Imail registry key from one server to another then
had to edit the whole thing manually? Disagree on this one.


-- 
Best regards,
 David                            mailto:[EMAIL PROTECTED]

---
[This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)]

---
This E-mail came from the Declude.JunkMail mailing list.  To
unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
type "unsubscribe Declude.JunkMail".  The archives can be found
at http://www.mail-archive.com.

Reply via email to