I added this TODO as a note about the ATTACH property to
objects. This is intended to specify file attachments for
objects--- perhaps an agenda, a document to be considered,
something like that. MS Outlook/Exchange implements
attachments poorly by allowing them to be executed. We need
not to replicate their mistakes, but we do need to allow
users of Net::ICal to access external files.
This IMO isn't really an interop issue, unless an MS
Exchange server passes iCal text with an attachment off to a
program that uses Net::ICal, and Exchange expects that
attachment to be executed by the receiver. But there's not
much we can do about that.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=11762
I added this TODO as a note about the ATTACH property to
objects. This is intended to specify file attachments for
objects--- perhaps an agenda, a document to be considered,
something like that. MS Outlook/Exchange implements
attachments poorly by allowing them to be executed. We need
not to replicate their mistakes, but we do need to allow
users of Net::ICal to access external files.
This IMO isn't really an interop issue, unless an MS
Exchange server passes iCal text with an attachment off to a
program that uses Net::ICal, and Exchange expects that
attachment to be executed by the receiver. But there's not
much we can do about that.
Logged In: YES
user_id=11762
I don't think this is really my bug personally to deal with;
it's more an "open issue" that should be dealt with when we
implement ATTACH.