Thanks, Unfortunately, LibJingle isn't _really_ written with that notion at all. It has the notion of multiple channels of media, but there really is no separation of media types. And there's only one list of codecs exchanged. It also seems to tie in a specific "session client" (and channel manager and media engine) with a specific content namespace. To me, it seemed easier to adapt the existing session-sessionclient infrastructure to have multiple sessions. At this point, I'm not so sure which was the "easiest" way to go (that's what I was shooting for with a prototype). I'm really not sure how I would have rearchitected LibJingle for multiple content with a single session & session client.
Anybody out there have any code??? Thanks again, Jeff --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "google-talk-open" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/google-talk-open?hl=en -~----------~----~----~----~------~----~------~--~---
