Java SIP Servlet is a software that helps in the development of Session Initiation Protocol (SIP) based communication applications. It offers a platform for developers to create scalable, secure, and reliable SIP-based applications that can handle real-time communication services.
Jiplet is a Java SIP Servlet that offers an open-source container for server-side SIP applications. With the Jiplet API, application developers can create Java-based SIP applications and deploy them directly in the container. The container comprises various framework services, such as support for SIP message parsing, formatting, scoped variables, authentication and authorization, thread-pooling, logging, custom class loading, management interface, and more.
The Jiplet container allows application developers to create server-side SIP applications utilizing a component-based model, which is similar to the one envisioned by the J2EE architecture. It aligns appropriately with the J2EE paradigm for software development and deployment. The software can work as a standalone Java application or as a service residing in a J2EE server, enabling the container to access several features offered by the J2EE server.
The Jiplet container has been built with the service provider model in mind so that a host can accommodate customized SIP applications from their customers securedly. This type of hosting is similar to the servlet hosting provided by many service providers. The Jiplet container's concept is very similar to a Java HTTP servlet container, wherein a Java HTTP servlet handles HTTP messages from web browsers. Similarly, a Jiplet is a Java class that handles SIP messages from SIP user agents.
The Jiplet container can host multiple SIP applications or contexts consisting of one or more jiplets, similar to the Apache Tomcat hosting one or more web applications. The jiplet container provides a set of Java classes that jiplet applications extend or use, similar to the servlet API authored by Sun Microsystems. The services offered by these classes are very similar to those of the servlet API, including scoped variables, request forwarding, and more.
Like a servlet container, the Jiplet container can deploy new jiplet applications, or contexts, using a zipped file called spr. However, there are notable differences between the HTTP and SIP protocols, which means that the servlet and jiplet containers are not the same. The Jiplet is not a formal specification like the servlet specification, and it is not an implementation of the SIP servlet specification (JSR 116) authored by Sun and its community of users.
Despite the differences, the jiplet and the SIP servlet have many similarities in terms of features, making the jiplet container a familiar tool for those familiar with SIP servlets. The developers plan to continue developing the Jiplet container based on feedback from the open-source community. In this way, they hope that open-source developers will extend this tool and the specification in place of a committee.
The Jiplet container allows application developers to create server-side SIP applications utilizing a component-based model, which is similar to the one envisioned by the J2EE architecture. It aligns appropriately with the J2EE paradigm for software development and deployment. The software can work as a standalone Java application or as a service residing in a J2EE server, enabling the container to access several features offered by the J2EE server.
The Jiplet container has been built with the service provider model in mind so that a host can accommodate customized SIP applications from their customers securedly. This type of hosting is similar to the servlet hosting provided by many service providers. The Jiplet container's concept is very similar to a Java HTTP servlet container, wherein a Java HTTP servlet handles HTTP messages from web browsers. Similarly, a Jiplet is a Java class that handles SIP messages from SIP user agents.
The Jiplet container can host multiple SIP applications or contexts consisting of one or more jiplets, similar to the Apache Tomcat hosting one or more web applications. The jiplet container provides a set of Java classes that jiplet applications extend or use, similar to the servlet API authored by Sun Microsystems. The services offered by these classes are very similar to those of the servlet API, including scoped variables, request forwarding, and more.
Like a servlet container, the Jiplet container can deploy new jiplet applications, or contexts, using a zipped file called spr. However, there are notable differences between the HTTP and SIP protocols, which means that the servlet and jiplet containers are not the same. The Jiplet is not a formal specification like the servlet specification, and it is not an implementation of the SIP servlet specification (JSR 116) authored by Sun and its community of users.
Despite the differences, the jiplet and the SIP servlet have many similarities in terms of features, making the jiplet container a familiar tool for those familiar with SIP servlets. The developers plan to continue developing the Jiplet container based on feedback from the open-source community. In this way, they hope that open-source developers will extend this tool and the specification in place of a committee.
What's New
Version 0.2.0: N/A