> I would like to implement the rtp specification.
> Is anyone else interested in helping with the design/code?
I would be glad to help, since I thought I would have to do this myself
anyway.
I think probably the best way to do it is just to start with a
packetizer. The output is just a collection of RTP packets,
appropriately stamped, etc.
Icecast does not currently have an RTP streaming layer, and that will
have to be implemented at some point as well. As long as we keep the
two independent, we should end up with a flexible architecture.
> Jack: i'm interested in your opinion on the difficulty of this since
you
> worked on the rfc spec.
Before you begin, there are a few warnings and suggestions:
- this is a draft. it will change. whatever code you write will need
modification as the draft changes. keep this in mind :)
- i have several edits to the draft that are minor trivial things, but I
would like to put them in before you start. i just want to incorporate
the feedback i got and flesh out a few sections.
- i would suggest that you only consider unicast rtp streams for
starters. the multicast method of reliably transmitting the codebooks
has still not been determined. and the ietf seems to think that
reliable multicast might be the best solution, which afaict doesn't
exist yet.
That's about it. What language are you planning to implement this in?
Icecast is currently written in C, and that's not likely to change.
jack.
--- >8 ----
List archives: http://www.xiph.org/archives/
Ogg project homepage: http://www.xiph.org/ogg/
To unsubscribe from this list, send a message to
'vorbis-dev-request@xiph.org'
containing only the word 'unsubscribe' in the body. No subject is
needed.
Unsubscribe messages sent to the list will be ignored/filtered.