Re: SDP wrapper? Object-oriented API?

No, and it should not. You need to code "something" or use any available JS
library.

--
Iñaki Baz Castillo
<ibc@aliax.net>
El 19/06/2013 17:10, "piranna@gmail.com" <piranna@gmail.com> escribió:

> So, technologically, would it be possible to "automagically" make the
> connection with the other end, and the developer don't worrying of any
> detail if he doesn't want?
>
> 2013/6/19 Roman Shpount <roman@telurix.com>:
> >
> > On Wed, Jun 19, 2013 at 10:56 AM, piranna@gmail.com <piranna@gmail.com>
> > wrote:
> >>
> >> So, for your answer, I should understand it would be done/masked using
> >> high-level libraries, but on the bottom frames of the stack (hidden by
> >> WebRTC API or not, like it's at this moment) an offer/answer exchange
> will
> >> be always required, isn't it?
> >
> >
> > No this is wrong. Offer/Answer is something that should be implemented in
> > JavaScript. What you need are much more basic operations, such as "get
> the
> > list of supported media types" , "get the list of codecs for a media
> type",
> > "select the transmit codec for a media stream", "pause/resume media
> stream"
> > etc. Currently offer/answer in webrtc is build on top of API like this.
> Look
> > at
> >
> https://code.google.com/p/webrtc/source/browse/#svn%2Ftrunk%2Fwebrtc%2Fvoice_engine%2Finclude
> > and
> >
> https://code.google.com/p/webrtc/source/browse/#svn%2Ftrunk%2Fwebrtc%2Fvideo_engine%2Finclude
> >
> > These are the API that are used internally. Wrapping them in JavaScript
> is
> > something that would make sense to me.
> >  _____________
> > Roman Shpount
> >
>
>
>
> --
> "Si quieres viajar alrededor del mundo y ser invitado a hablar en un
> monton de sitios diferentes, simplemente escribe un sistema operativo
> Unix."
> – Linus Tordvals, creador del sistema operativo Linux
>