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

[Alec Dun <AlecDu@xxxxxxxxxxxxxxxxxxxxxx>]

I would agree about it being easier to parse (and the reason is because
it doesn't do 1/2 as much, if it was as good as MIME, it would be just
as much code as MIME).  One key problem is that in all proposals I've
seen, you need BOTH MIME and vCalendar parsing code.  Wouldn't we be
better off just having MIME?  That way implementers don't have to have
extra code and understand extra concepts and everything.  It just
complicates things.

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.

Speak up now if your company likes small, efficient products.

- Alec.

> ----------
> From:
> owner-ietf-calendar@imc.org[SMTP:owner-ietf-calendar@imc.org] on
> behalf of Keith Moore[SMTP:moore@cs.utk.edu]
> Sent: 	Friday, December 6, 1996 4:35 PM
> To: 	Lewis Geer (Exchange)
> Cc: 	'Mike Weston'; ietf-calendar@imc.org; moore@cs.utk.edu
> Subject: 	Re: MIME as a vCalendar element separator - bad move... 
> 
> 
> > I have yet to hear a reason why the 
> > vcalendar separators are *better* than using MIME.  What additional 
> > functionality do they give that MIME does not have?
> 
> vCalendar framing is MUCH easier to parse than MIME.
> 
> Keith
>