Doesn't work at all. Got this on startup and on any attempt to change folder (which fail)
can't read "flist(seqcount,lists/exmh,unseen)": no such element in array
(reading value of variable to increment)
"time [list  FolderChange $folder $msgShowProc"

from localhost (localhost [127.0.0.1])
	by phobos.labs.netnoteinc.com (Postfix) with ESMTP id 1938343F99
	for <jm@localhost>; Wed, 28 Aug 2002 09:47:19 -0400 (EDT)
from phobos [127.0.0.1]
	by localhost with IMAP (fetchmail-5.9.0)
	for jm@localhost (single-drop); Wed, 28 Aug 2002 14:47:19 +0100 (IST)
from xent.com ([64.161.22.236]) by dogma.slashnull.org
    (8.11.6/8.11.6) with ESMTP id g7SDekZ26573 for <jm@jmason.org>;
    Wed, 28 Aug 2002 14:40:47 +0100
from lair.xent.com (localhost [127.0.0.1]) by xent.com (Postfix)
    with ESMTP id 57A2C29418C; Wed, 28 Aug 2002 06:38:10 -0700 (PDT)
from hotmail.com (oe34.law12.hotmail.com [64.4.18.91]) by
    xent.com (Postfix) with ESMTP id CB26E29409A for <fork@xent.com>;
    Wed, 28 Aug 2002 06:37:51 -0700 (PDT)
from mail pickup service by hotmail.com with Microsoft SMTPSVC;
    Wed, 28 Aug 2002 06:39:56 -0700
From fork-admin@xent.com  Wed Aug 28 14:47:26 2002

> Now, to do this, we all know they have to be cracking the strong crypto used
> on all transaction in order to process them... So this has some preaty heavy
> implications, unless it's just BS.
Anybody buying a box like this is undoubtledly going to integrate it into their
crypto infrastructure.  What's the point of putting in a box like this if it's
not an active participant in your security framework?
> Or.... you could just not bloat it 20x to begin with. Nah! (that was the
> whole point of XML afterall, to sell more CPUs - much like Oracle's use of
> Java allows them to sell 3x more CPU licenses due to the performance hit)
Blah, blah, blah.  The marketing FUD gets compounded by the Beberg FUD, talk
about 20x bloat.
> Again, see above... they _are_ claiming to decode the crypto...
What gives you the impression that's what they're doing?  That's not what the
text says.  It's largely fluff anyway.
> > "Our XG3 execution core converts XML to machine code," said Kelly,
> Mmmmmmmmmmm, machine code, never a good idea ;)
Uhhh, fundamentally it's all machine code.  Kelly's comment seems more like
drivel from a clueless marketroid than anything of technical concern.
Having what appears to be a silicon XML router would be a cool thing.  Having
one integrated with your crypto environment would kick ass.  Let it
deserialize/decrypt/repackage the XML before handing it off to the app servers.
The question, of course, is does it work with actual applications in the field
without tremendously reworking them.  Somehow I doubt it...
-Bill Kearney