<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <title>About CUP API</title>
  <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_thread?p_l_id=&amp;threadId=2000456" />
  <subtitle>About CUP API</subtitle>
  <id>http://developer.cisco.com/c/message_boards/find_thread?p_l_id=&amp;threadId=2000456</id>
  <updated>2013-05-21T17:59:23Z</updated>
  <dc:date>2013-05-21T17:59:23Z</dc:date>
  <entry>
    <title>RE: About CUP API</title>
    <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=2000464" />
    <author>
      <name>David Staudt</name>
    </author>
    <id>http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=2000464</id>
    <updated>2010-04-16T09:30:52Z</updated>
    <published>2010-02-27T01:20:37Z</published>
    <summary type="html">SOAP is XML over HTTP, which is not unix or windows (or device) dependent
Same with REST
SIP is a network wire protocol, so again not OS/device dependent
 
There are OS/language native libraries (available on the web, etc.) which can encapsulate the above - for example Apache Axis, which can generate native Java language code stubs for SOAP services (.NET has a SOAP compiler which does the same thing for Windows,) or a third party SIP stack which would encapsulate the SIP protocol in a C++ API.</summary>
    <dc:creator>David Staudt</dc:creator>
    <dc:date>2010-02-27T01:20:37Z</dc:date>
  </entry>
  <entry>
    <title>RE: About CUP API</title>
    <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=2000462" />
    <author>
      <name>Shwetha Sanjeev</name>
    </author>
    <id>http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=2000462</id>
    <updated>2010-04-16T09:30:52Z</updated>
    <published>2010-02-27T01:20:37Z</published>
    <summary type="html">For example, some API's are based on Unix system calls, others on windows APIs.
They may be device specific also.
 
Regards,
Ramesh S</summary>
    <dc:creator>Shwetha Sanjeev</dc:creator>
    <dc:date>2010-02-27T01:20:37Z</dc:date>
  </entry>
  <entry>
    <title>RE: About CUP API</title>
    <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=2000459" />
    <author>
      <name>David Staudt</name>
    </author>
    <id>http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=2000459</id>
    <updated>2010-04-16T09:30:52Z</updated>
    <published>2010-02-27T01:20:37Z</published>
    <summary type="html">CUP has 3 APIs that can be useful to applications:
 
- SOAP API - Configuration/provisioning, presence status via polling or notification using XML over HTTP SOAP
- REST API - Configuration/provisioning, presence status via HTTP/REST
- SIP SIMPLE - Presence status, via SIP protocol
 
Not sure what you mean by 'modelled on which Operating System API?'</summary>
    <dc:creator>David Staudt</dc:creator>
    <dc:date>2010-02-27T01:20:37Z</dc:date>
  </entry>
  <entry>
    <title>About CUP API</title>
    <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=2000455" />
    <author>
      <name>Shwetha Sanjeev</name>
    </author>
    <id>http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=2000455</id>
    <updated>2010-04-16T09:30:52Z</updated>
    <published>2010-02-27T01:20:37Z</published>
    <summary type="html">Could you please tell me that CUP API is modelled on which Operating System API?
 
Regards,
Ramesh S</summary>
    <dc:creator>Shwetha Sanjeev</dc:creator>
    <dc:date>2010-02-27T01:20:37Z</dc:date>
  </entry>
</feed>

