SailFin CAFE, like other converged application development frameworks has changed the converged application development paradigm. Having used CAFE APIs so far, if one thought that application development has never been so fast and so easy, things just got better with v1 b28.
Converged (Http/SIP) applications gives users the flexibility of creating or accessing information about their communications (call/conferences/im ...) over the web. To make this possible a typical converged application would contain an entry point for all the Http requests, which is mostly an Http Servlet.
Overload protection feature has been part of earlier releases of SailFin, lets start by describing the what can be improved in the current implementation.
Lots of fixes have gone into SailFin 2.0, some of these fixes are related to functionality whereas others are to improve performance. The changes sometimes required creation of new user configurable properties in order to extract the optimal-performance/desired-behavior depending on the users deployment.
High availability in SailFin can be achieved by deploying a cluster of instances and configuring the load balancer and the replication modules as per the user's needs.
(Simple Traversal of User Datagram Protocol (UDP) Through Network Address Translators (NATs), define
Generic JMS RA 2.0 is available as an alpha version download today, we are working towards promoting it to a release. One of the main features in 2.0 is the ability to use JMS providers that do not support Chapter 8 (Asynchronous message delivery).
SailFin has been designed to provide a certain quality of service in
terms of the response times, call rate, etc ..
Throughput, stress and longevity metrics of the SailFin SIP container depends on a few factors that can be controlled and configured by the end user, and getting the right size of the buffers used internally is one of them.
SailFin SIP container requires threads to do various tasks like process an incoming request, send a response, execute timers and initiate new requests with clients. The threads required to perform these tasks are obtained from thread pools which are specifically created and configured for the sip-service in SailFin.