Homepage | Products | OX Knowledge Base | Support | Try Now | Contact | Company
OX Logo
Results 1 to 6 of 6
  1. #1

    Default Detailed Task and Appointment Data - Ids 224-229

    Dear OX Team,

    I am reviewing the HTTP API. I have one question regarding the Ids 224-229 of the Detailed Task and Appointment Data structure. Why do you not move these ids to the Detailed Appointment Data structure? These ids are only appointment specific and are not valid for tasks.

    Best regards,
    Thomas

  2. #2
    Join Date
    Feb 2007
    Posts
    253

    Default

    Because these fields do apply to tasks, they are just not implemented (yet).

  3. #3

    Default

    So why not move the ids until they are implemented? :-)

  4. #4
    Join Date
    Feb 2007
    Posts
    253

    Default

    Because that would mean these fields don't apply to tasks, which it not true.

  5. #5

    Default

    I moved them anyway in my implementation. So do you have a time estimate until when you will implement them? Do we talk about weeks or years?

    Best,
    Thomas

  6. #6
    Join Date
    Feb 2007
    Posts
    253

    Default

    Currently, we're talking about "if". The iCalendar standard specifies them for both tasks and appointments, but we've yet to see any task scheduling actually used "in the wild".

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •