[OSM-dev] TRAPI status

[Peter Körner]

>     I started working on a streaming XML output plugin for Osmosis. I
>     was intending to take advantage of PuSH/PubSubHub messaging and
>     maybe even XMPP (so that you get a 1-min delayed IM when someone
>     changes something in your bbox).
> 
>     Anyway, TRAPI could use this same plugin to apply updates to their
>     database.
> 
> 
> I've also spent a fair bit of time thinking about this type of thing.  
> When I first started work on the replication diffs I had in mind a 
> server-side daemon (using Osmosis internally) that would push changes to 
> all connected clients.  It would allow a client to connect, specify 
> which replication number it was up to, receive all updates in a single 
> stream, then continue to receive live changes as they occurred.

Unless there is some kind of filtering involved, i don't see the 
advantage over the current replication approach (despite of bandwidth, 
maybe).

But if I can subscribe to all changes in a bbox or to all changes on 
ways with a highway-tag, then there's a real big benefit, as i don't 
have to deal with all changes (which is quite a huge amount of data) but 
only with those things I'm interested in.

Peter