Re: Issue 2879 in reviewboard: support for event streams

[reviewboard]

Comment #1 on issue 2879 by rajas...@gmail.com: support for event streams
http://code.google.com/p/reviewboard/issues/detail?id=2879

Apologize if this is a naive question , but doesnt the django signals do  
the "publishing" part of the event. Right now, reviewboard throws certain  
events during the lifecycle of a review process, which can be caught by  
listeners to do certain actions. The catch is that, its synchronous but  
this post  
(http://www.chrisdpratt.com/2008/02/16/signals-in-django-stuff-thats-not-documented-well/)  
talks about running things asynchronously and there are definitely other  
ways of doing it than mentioned in the thread.


Is the DBus option provided an alternative to the sending part of django as  
well ?


--
You received this message because you are subscribed to the Google Groups 
"reviewboard-issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard-issues+unsubscr...@googlegroups.com.
To post to this group, send email to reviewboard-issues@googlegroups.com.
Visit this group at http://groups.google.com/group/reviewboard-issues?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Issue 2879 in reviewboard: support for event streams

[reviewboard]

Status: New
Owner: 
Labels: Type-Enhancement Priority-Medium

New issue 2879 by matthew@kitware.com: support for event streams
http://code.google.com/p/reviewboard/issues/detail?id=2879

What version are you running?
RB 1.7.1

Describe the enhancement and the motivation for it.
It would be really great if RB supported event streams a la  
http://gerrit.googlecode.com/svn/documentation/2.1.2/cmd-stream-events.html  
(especially for porting third-party tools - e.g. auto-builders - using  
gerrit event streams to RB).


Please provide any additional information below.
Obviously this is a candidate for an extension, but would be a neat place  
to start on a pool of 'official' extensions.


The 'tricky' part is what to use for IPC, since the RB server needs to be  
able to throw events 'over the wall' to any listeners that may (or may not)  
exist at the time. With Linux now being the only supported platform, one  
possibility is to use the dbus system bus that exists on most modern Linux  
systems. To that end, in the hope it may be useful, I've attached some  
initial experiments I did in that direction. The client (dbus-cli.py) is  
more or less complete, except would obviously need to be named differently.  
The server component would optimally be integrated into the extension (so,  
basically take the dbus-srv.py code and meld it onto something based on  
RBWebHooks, with a more complete signal set). The dbus config to allow use  
of the system bus would be a template that needs to be modified by the site  
installer to have the appropriate context for the RB server, based on how  
the RB server is set up.


Attachments:
dbus-srv.py  938 bytes
dbus-cli.py  454 bytes
org.reviewboard.EventStream.conf  773 bytes

--
You received this message because you are subscribed to the Google Groups 
"reviewboard-issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard-issues+unsubscr...@googlegroups.com.
To post to this group, send email to reviewboard-issues@googlegroups.com.
Visit this group at http://groups.google.com/group/reviewboard-issues?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.