Net::ICal::Event needs to be validating the data it
gets input a bit more tightly. It relies on ETJ's
validation routines right now, which is just not
enough.
Be careful about what you require, though. For example
the docs for Net::ICal::Event indicate an organizer is
required.
If the VEVENT is coming from a calendar that you don't have
permission to read (it's a confidential or private event),
you
probably can't read the ORGANIZER, or even UID. About all
you're likely to get is the dtstart and either the duration
or
the dtend.
This is the way Steltor's "CorporateTime" works -- if I
schedule
a private event and someone else looks at my calendar, they
can get the DTSTART and the DURATION, but that's it.
Nothing
else.
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=9786
What's the RFC section for this?
Logged In: YES
user_id=1366
Changed bug so it covers all validation problems. We need to
consistently put in validation routines
for every component.
Logged In: YES
user_id=36222
Be careful about what you require, though. For example
the docs for Net::ICal::Event indicate an organizer is
required.
If the VEVENT is coming from a calendar that you don't have
permission to read (it's a confidential or private event),
you
probably can't read the ORGANIZER, or even UID. About all
you're likely to get is the dtstart and either the duration
or
the dtend.
This is the way Steltor's "CorporateTime" works -- if I
schedule
a private event and someone else looks at my calendar, they
can get the DTSTART and the DURATION, but that's it.
Nothing
else.