Extension architecture help required

[Byron Jones]

hey gerv,

Gervase Markham wrote:
> In my Sync extension:
> http://bzr.mozilla.org/bugzilla/extensions/sync/
> I am using the bug_end_of_update hook to do syncing once a bug is
> updated.
i have an extension which is designed to push updates to other systems 
which currently poll bugzilla for updates (pulse, elastic search caches, 
metrics, etc).
https://github.com/globau/bugzilla-push
it's extremely close to completion, and is a q2 goal.

i deal with the issue you've encountered by performing serialisation of 
the bug at the time the update is made, in my case to JSON.  these are 
inserted into a custom table which a custom daemon polls and sends.  i 
don't use the jobqueue system because that doesn't guarantee the order 
of the messages, which is important when you're sending update messages 
(especially when a remote system is down).

since i already have a working system for sending bug updates which 
deals correctly with ordering of the updates, as well as queuing 
messages when the remote system is down, another option would be for the 
update-pushing part of your extension to utilise my bugzilla-push 
extension and be dropped in as another connector.  see 
https://github.com/globau/bugzilla-push/tree/master/Push/lib/Connector



-byron
-- 
byron - irc:glob - bugzilla.mozilla.org team -

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bugzilla.org/pipermail/developers/attachments/20120430/aa58b0ff/attachment.html>