Mobicents collaboration is in the works in today's Forums. In SIP RA Type, ben_evans writes: "Hi all, my name is Ben Evans and I work at Open Cloud writing SIP RAs and services. I see has Ranga mentioned me in an earlier thread - we have talked in the past about cooperating on a common JAIN SIP RA Type definition, however not much has been done yet, so I would like to kick off a discussion here. My goal would be for us to converge on a "standard" RA Type so that SIP SBBs can be easily portable between Mobicents and Open Cloud's Rhino SLEE, and others. I think they are probably pretty similar already, both based on the SLEE spec recommendation, so this should not be too difficult."

tmarble reposts some important considerations Re: Java EE postings: "In many environments when we look at performance, database performance turns out to be at least as crucial as appserver performance per se. One of the most significant ways this manifests itself is in JDBC statement caching. Statement caching allows the database to reuse the SQL plan for a particular query, which greatly improves the performance of the database (and hence your appserver). It's crucial that you write your Java EE application to allow statement caching. If you're using CMP (or something else where the containter generates the JDBC calls), you can be assured that your appserver does the right thing. If you are writing servlets with your own JDBC calls, it's up to you: you must use prepared statements, and the text of the prepared statement must be the same in order for statement caching to work."