[reSIProcate] Client side SIP framework performance

[Emmanuel BUU]

Nilay Tripathi wrote:

> Hi,
>
> I was looking for some performance figures of reSIProcate stack when 
> run at client-side.
> The motive is to evaluate it against with some Java based client side 
> SIP framework as
> more and more big players are towards this.
>
> I want to ask, what benefit do we get in deploying C/C++ based client 
> side SIP framework
> as against Java based ones.

> I know that Java being an interpreted language may not be
> able to catch up with C/C++ based framework, but on the other side of 
> the coin Java does
> gives the flexibility to add new apps. with ease and issue of speed 
> might not be very
> relevant given the new generation of the fast hardwares.


If by client, you mean standalone SIP phone sitting on PC. To be honest, 
there is not much difference. However, modern soft phones also processes 
video. I am not sure Java is very indicated to decode & display crisp, 
fluid video stream. Not talking about encoding. So basically, you would 
end up coding the SIP in Java and the RTP & media processing in C / C++. 
Mucho hassle.

I have heard about a Java Media Framework. I do not know what is the 
performance of it.

Personally I dislike java based desktop programs as I tend to find them 
memory hungry and not very reactive.

If by client, you mean SIP application server and back to back user 
agent, Java has here a clear advantage in term of dev speed and 
integration with external environments (database, http). And yes, here 
you're right. Fast server are now available and can offset easily the 
performance gap with C/C++ based software.

Now if you are going to do any RTP processing on the server side too, 
C/C++ enviroment are to me the fittest. But I am an old grumpy developper.

> Any thoughts !!

Are you suggesting that you are buiding a Java version or reSIProcate?  
Great :).