Re: [Standards] New XMPP Use Case: Private Media Networks

2008-05-21 Thread Dirk Meyer
Hi, Dave Cridland wrote: This looks interesting. Particularly so because of the case allowing information flow between public services and private media services. I'm thinking particularly of data stores such as the BBC's Programmes thing, but this would be equally applicable to a number of

Re: [Standards] UPDATED: XEP-0166 (Jingle)

2008-05-21 Thread Tim Julien
The Changelog says content-modify and content-accept were removed from the PENDING state. But the state diagram in section 5.1 still lists them as valid actions when in PENDING. -Tim Julien XMPP Extensions Editor wrote: Version 0.25 of XEP-0166 (Jingle) has been released. Abstract: This

Re: [Standards] UPDATED: XEP-0167 (Jingle Audio via RTP)

2008-05-21 Thread Tim Julien
This makes use of content-replace in the PENDING state (i.e., before session-accept) as the final step in transport negotiation. see the state diagrams and examples in sections 9.2, 9.3. However, Jingle (166) is very clear that content-replace cannot be used in the PENDING state. Section

Re: [Standards] UPDATED: XEP-0176 (Jingle ICE-UDP Transport Method)

2008-05-21 Thread Tim Julien
This makes use of content-replace in the PENDING state (i.e., before session-accept) as the final step in transport negotiation. see the state diagrams and examples in sections 5.1, 5.6. However, Jingle (166) is very clear that content-replace cannot be used in the PENDING state. -Tim

Re: [Standards] UPDATED: XEP-0234 (Jingle File Transfer)

2008-05-21 Thread Tim Julien
So, I'm confused about some of the transport negotiation stuff. In first scenario (section 3.1) the negotiation occurs after session-accept - which is counter to every Jingle spec that has come out so far: typically both description and transport are negotiated as a pre-requisite to

Re: [Standards] UPDATED: XEP-0166 (Jingle)

2008-05-21 Thread Peter Saint-Andre
Thanks for your feedback here and in the other threads. I've gotten behind on the Jingle edits but will work on them again very soon so that we can finish these specs! On 05/21/2008 12:35 PM, Tim Julien wrote: The Changelog says content-modify and content-accept were removed from the PENDING

[Standards] Pub/Sub RSS

2008-05-21 Thread Kelly S
Hi all. I am just getting back into XMPP after a few years away from it and I am digging into the Pub/Sub XEP. I am looking for a bit of feedback. I am writting the service which will pull data from RSS and publish it via Jabber. However I need a way to relate the unique RSS url to the XMPP

Re: [Standards] Pub/Sub RSS

2008-05-21 Thread Peter Saint-Andre
On 05/21/2008 6:26 PM, Kelly S wrote: Hi all. I am just getting back into XMPP after a few years away from it and I am digging into the Pub/Sub XEP. I am looking for a bit of feedback. I am writting the service which will pull data from RSS and publish it via Jabber. However I need a way to

Re: [Standards] Pub/Sub RSS

2008-05-21 Thread Kelly S
Thanks for the reply! I took a look at what your saying about NodeID and I understand a bit more clearly now. Wow the Pub/Sub spec is large! Anyways. I'm thinking of writing a service where users can subscribe to feeds off the web. A service will be monitoring all feeds and pulling the