Re: MIME as a vCalendar element separator - bad move...

[Ken Shan <ken@xxxxxxxxxxx>]

Paul Rarey wrote:

> Alec Dun wrote:

> > The only argument I've seen so far is a vCalendar backward
> > compatibility argument, but I would rather pay the compatibility price
> > (since there isn't really much vCalendar out there) than bloat the code
> > with all this extra parsing code.  I think customers want everyone's
> > code to be fast and small so they don't have to buy so much memory for
> > their machines.

> It's hard to say no to a statement like that. It would seem a reusable
> JAVA based MIME parser would help such that each application specific
> component wouldn't have to include it's own MIME parser. 

Exactly how much code (in Java, say) is a MIME parser?  How much code
is a hack on top of the MIME parser, for those who have it, to make it
translate BEGIN/END markers into recursive MIME objects?

It was argued that no personal digital assistants can ignore the
Internet today.  Excuse my ignorance on this matter, but how much
memory does a typical Windows CE palmtop machine has?  How much memory
would be used on a typical Windows CE palmtop in order to implement
MIME parsing?  How much would be used to implement BEGIN/END parsing?
How much memory does Exchange and Schedule+ occupy on a typical
Windows CE machine?  I think some hard numbers would help greatly.

-- 
blue | Ken; Shan, Chung-chieh; Sian7, Tiong1-kiat8; ken@digitas.harvard.edu.
 ()  | Your code today becomes the mind tomorrow:  Your plan its means,
 /\  | your dream its ends, your ideal its elegance.  Hack on.