Hi Said,

Sorry for the long delay in replying.


said nabirh wrote:[...]
Zap is already split up into 'generic' sip/sdp/media apis and a client 
application. The apis live in the xulrunner components directory, 
whereas the zap application chrome (which contains most of the stuff you 
want to strip out) lives under xpi-stage/zap/.
The best way is to build zap as is, but add your own xulrunner 
application project. E.g. you can add the application directories and 
appropriate Makefiles under mozilla/zap/my_minimal_zap_chrome/ or you 
can follow 
http://developer.mozilla.org/en/docs/Getting_started_with_XULRunner.

You can then use all the sip/sdp/zmk apis in your application code, much 
like the zap chrome does (Components.utils.importModule(..) or 
Components.classes[...].getService(..)). These are all installed as part 
of zap-the-framework and are available to any application that is built 
on top of the zap xulrunner. You can look at 
http://www.croczilla.com/~alex/zap/doc/html/
for the up-to-date api 
documentation and take zap.js/zap.xul as guidance.

Cheers,
Alex

Hi Jean-Michel,

jean-michel fan_de_teamspeak wrote:[...]

The video support needed in Zap is for realtime video, not streaming 
video.  Realtime video has very different constraints.
[...]

[...]