[Twisted-Python] OSC protocol implementation
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi list, some months ago, I created an implementation of the OSC protocol [1] in twisted, together with Alexandre Quessy. I've put it to review but so far nobody has responded to it: http://twistedmatrix.com/trac/ticket/4196 As stated in the ticket we'd like to release and maintain this as part of twisted but we'd also like to release this soon(ish). So my question is: what are your opinions about including the OSC protocol as a standard part of twisted and what will be the expected time frame for such a thing to happen? Arjan [1] http://bitbucket.org/arjan/twisted-osc/overview/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkvVrC0ACgkQigE4AbflYerTFACbB96SZZ4Q9euf3aEl9ARoiKnw K/EAn3Vs5otRXgdwohXLHK/S2xbc4rZD =27wB -----END PGP SIGNATURE-----
On 03:07 pm, arjan@scherpenisse.net wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi list,
some months ago, I created an implementation of the OSC protocol [1] in twisted, together with Alexandre Quessy.
I've put it to review but so far nobody has responded to it: http://twistedmatrix.com/trac/ticket/4196
Hi Arjan, Just a point of procedure, the ticket is not actually in "review" as the Twisted development process understands it. Tickets with the "review" keyword are in review, and receive particular attention. Other tickets easily get lost in the large pile of open tickets.
As stated in the ticket we'd like to release and maintain this as part of twisted but we'd also like to release this soon(ish).
So my question is: what are your opinions about including the OSC protocol as a standard part of twisted and what will be the expected time frame for such a thing to happen?
This is mainly a question of when someone finds it interesting enough to review the code. Personally, while I remember commenting on that ticket a couple months ago, I had to go re-read the wikipedia page to remember what OSC is. Since this is a protocol I've never come across before and which I can't think of any immediate applications that are relevant to me, it's not likely I'll spontaneously go review the code. Perhaps there is another developer who would be interested in this who will do so. Posting on the list is a good way to try to get attention, as is asking in the Freenode #twisted irc channel. If you can't find someone who wants to review it just because they're interested, you might be able to trade for a review of another ticket. Hope this helps, Jean-Paul
On Mon, 2010-04-26 at 15:56 +0000, exarkun@twistedmatrix.com wrote:
This is mainly a question of when someone finds it interesting enough to review the code. Personally, while I remember commenting on that ticket a couple months ago, I had to go re-read the wikipedia page to remember what OSC is. Since this is a protocol I've never come across before and which I can't think of any immediate applications that are relevant to me, it's not likely I'll spontaneously go review the code. Perhaps there is another developer who would be interested in this who will do so. Posting on the list is a good way to try to get attention, as is asking in the Freenode #twisted irc channel. If you can't find someone who wants to review it just because they're interested, you might be able to trade for a review of another ticket.
As a worst case alternative if time becomes an issue, you can release this as a standalone project (many Twisted libraries have begun prefixing package names with tx, e.g. txAMPQ). It can always be merged later with Twisted if there's an interest (as long as the license doesn't conflict).
Hello,
2010/4/26 Itamar Turner-Trauring
On Mon, 2010-04-26 at 15:56 +0000, exarkun@twistedmatrix.com wrote:
This is mainly a question of when someone finds it interesting enough to review the code. Personally, while I remember commenting on that ticket a couple months ago, I had to go re-read the wikipedia page to remember what OSC is. Since this is a protocol I've never come across before and which I can't think of any immediate applications that are relevant to me, it's not likely I'll spontaneously go review the code. Perhaps there is another developer who would be interested in this who will do so. Posting on the list is a good way to try to get attention, as is asking in the Freenode #twisted irc channel. If you can't find someone who wants to review it just because they're interested, you might be able to trade for a review of another ticket.
As a worst case alternative if time becomes an issue, you can release this as a standalone project (many Twisted libraries have begun prefixing package names with tx, e.g. txAMPQ). It can always be merged later with Twisted if there's an interest (as long as the license doesn't conflict).
Yes, I guess we should use it a bit in productions so that we test it thorougly. It won't be in the release in early June, so I guess we should call it txosc for a few months before we submit it again to be merged. The API might change while I use it in some projects. Note that it is fully working right now, and we have completed the unit tests. My only concern is this: if we make it a standalone project, I might want to split it in three files, whereas it is in just one right now. Maybe it's ok to create a subpackage in the in twisted.prototocols, though, like the "gps" and "mice" subpackages. Thanks, Alex
_______________________________________________ Twisted-Python mailing list Twisted-Python@twistedmatrix.com http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
-- Alexandre Quessy http://alexandre.quessy.net/
participants (4)
-
Alexandre Quessy -
Arjan Scherpenisse -
exarkun＠twistedmatrix.com -
Itamar Turner-Trauring