Cipango 3.0.0.M0 released

[Nicolas]

Hi all,
We've just released cipango 3.0.0.M0 which brings many fixes and improvements.
The main changes are that

• It is now based on Jetty-9; 
• Jetty integration has been revamped so that it may reuse several Jetty components while achieving a looser coupling;
  
• Performance has been improved by using NIO ;
• Web console has been redesigned to use Boostrap and Velocity libraries;
• Integration tests and a client has been added.
  

Documentation is available on confluence.cipango.org and distribution at repository.cipango.org. We will try to improve documentation for 3.0.0.M1 release.
Next minor versions will focus on DNS (RFC 3263) support and OSGi.

Cipango Team

[Chris Lauwers]

Hi, I recently started looking at Cipango. I've worked with Mobicents a bit, but I'm intrigued by Cipango since it is based on Jetty, and I like Jetty since I can embed it in my application code. It appears, however, that Cipango isn't simply an add-on to Jetty, but rather that it comes with its own (slightly modified) distribution of Jetty. I'm curious as to why this is? Is this because of limitations of Jetty? If so, I'd love any detail about what those limitations are. Have there been any discussions about complete decoupling?

Many thanks,

Chris

[David Soulayrol]

Hello Chris.

On 2013.02.22 11:33:01 -0800, Chris Lauwers wrote:

> Hi, I recently started looking at Cipango. I've worked with Mobicents a
> bit, but I'm intrigued by Cipango since it is based on Jetty, and I like
> Jetty since I can embed it in my application code. It appears, however,
> that Cipango isn't simply an add-on to Jetty, but rather that it comes with
> its own (slightly modified) distribution of Jetty. I'm curious as to why
> this is? Is this because of limitations of Jetty? If so, I'd love any
> detail about what those limitations are. Have there been any discussions
> about complete decoupling?

Actually Cipango is built and runs on top of pristine Jetty. The core of
Cipango lies in the cipango-sip and cipango-server projects, the other
ones being tools for development, execution, tests or deployment.

The project cipango-distribution packages all this within a Jetty
distribution. The Jetty distribution is not altered at all: it is
completed with the archives and the configuration files from Cipango. If
you tweak the distribution's configuration to not load Cipango (for
Cipango 3, try moving 100-sip.ini out of start.d), and run 'jetty.sh' or
launch 'java -jar start.jar' you still have a pure Jetty running.


PS: please do not cross-post on both cipango lists.

--
David Soulayrol

[Vadim Tsyganok]

Guys, it appears that your confluence site is down.

Side question:do you have any rough ETAs on M1 (I am quite interested in RFC 3263)

-Vadim

On Monday, January 7, 2013 8:35:48 AM UTC-8, Nicolas wrote:

[David Soulayrol]

Hello,

On 2013.03.14 22:55:29 -0700, Vadim Tsyganok wrote:

> Guys, it appears that your confluence site is down.

Yes, thanks. Confluence is now restarted.

> Side question:do you have any rough ETAs on M1 (I am quite interested in
> RFC 3263)

I'm sorry I can't provide you a satisfying response. Because of poor
availability of the team in the next few weeks, there will be only small
changes if there are any changes at all.

We have begun to think about the implementation of RFC3263, so there is
no major hurdle and this will be done as soon as we will have the
opportunity to work on it.

--
David Soulayrol

[Chris Lauwers]

Is there any on-line JavaDoc for Cipango 3.0.0?

thanks,

Chris

On Monday, January 7, 2013 8:35:48 AM UTC-8, Nicolas wrote:

[Nicolas]

Hello Chris,
There is no online Javadoc, but javadoc and source code is available on our maven repository at http://repository.cipango.org/

If you use maven and eclipse for your project, you could access to source code or javadoc from eclipse

• by using the m2e eclipse plugin
  
• by using the following command: mvn eclipse:eclipse -DdownloadSources -DdownloadJavadocs

Kind regards,
Nicolas