RE: RE[2]: begin/end as a vCalendar element separator - bad move...

[Alec Dun <AlecDu@xxxxxxxxxxxxxxxxxxxxxx>]

Ken,

I wasn't intending to exaggerate, hopefully it's small, like less than
52k.

The point is that to make small products, one can't just say oh so what,
I can afford to spend 52k here and 52k there.  All those 52ks add up and
make a large product.  To make something small, one needs to always
question, saying "can I achieve the same functionality and not pay that
cost?"  That is the attitude one needs.

In this case, I think the answer is "yes" here.

Thanks,
Alec.

> ----------
> From:
> owner-ietf-calendar@imc.org[SMTP:owner-ietf-calendar@imc.org] on
> behalf of Ken Shan[SMTP:ken@digitas.org]
> Sent: 	Saturday, December 7, 1996 9:23 PM
> To: 	Alec Dun
> Cc: 	mark@lucent.com; izzy@nugget.scr.atm.com; skip@calendar.com;
> ietf-calendar@imc.org
> Subject: 	Re: RE[2]: MIME as a vCalendar element separator - bad
> move...
> 
> 
> Alec Dun wrote:
> 
> > How many people are intending to build calendaring products that
> will
> > not be capable of sending meeting requests to others via e-mail?
> 
> We are.  On the sending side we plan to have Web-downloadable event
> schedules (in particular courses); on the receiving side the user
> either drags these to their own calendaring application or uses a Java
> applet.  For simple unidirectional exchanges like these we don't
> really need MIME.
> 
> I cannot understand why the issue of code bloat is being exaggerated
> so much, or maybe I just don't understand the issue.  From what I
> understand, we're trying to decide whether we should put BEGIN/END
> around calendar objects.  I assume that even if we do have BEGIN/END,
> we'd still want to encapsulate the whole thing inside a MIME part.  If
> each part is limited to one calendar object, it takes one line of code
> to skip BEGIN/END "pseudo-properties" if one doesn't want to see them.
> If each part can consist of multiple calendar objects, it takes maybe
> ten lines to simulate a new (recursive) MIME part for each BEGIN if
> one would prefer to see it that way.  Or did I miss something?
> 
> -- 
> 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.
>