SIP servlets differ from typical HTTP servlets used in web applicationsin the following ways:
HTTP servlets have a particular context (called the context-root)in which they run, while SIP servlets have no context.
HTTP servlets typically return HTML pages to the requestingclient, while SIP servlets typically connect SIP-enabled clients to enabletelecommunications between the client and server.
SIP is a peer-to-peer protocol, unlike HTTP, and SIP servletscan originate SIP requests, unlike HTTP servlets which only send responsesto the originating client.
See AlsoIntroduction to SIPSIP servlets often act as proxies to other SIP endpoints,while HTTP servlets are typically the final endpoint for incoming HTTP requests.
SIP servlets can generate multiple responses for a particularrequest.
SIP servlets can communicate asynchronously, and are not obligatedto respond to incoming requests.
SIP servlets often work in concert with other SIP servletsto respond to particular SIP requests, unlike HTTP servlets which typicallyare solely responsible for responding to HTTP requests.