I have this wild idea of modifying GeoServer to produce a geoRSS stream whn people make transations on the WFS. Thus if someone adds a polygon to the WFS/T I could “watch” the changes being made using a GeoRSS reader (eg http://brainoff.com/gmaps/mgeorss.html).
I just spoke to Chris and he thinks this might fit with other notification methods people are proposing. So does anyone else have any thoughts which would save me some thinking?
Ian
–
Ian Turton
http://www.geotools.org
Ian Turton wrote:
I have this wild idea of modifying GeoServer to produce a geoRSS stream whn people make transations on the WFS. Thus if someone adds a polygon to the WFS/T I could "watch" the changes being made using a GeoRSS reader (eg http://brainoff.com/gmaps/mgeorss.html).
I just spoke to Chris and he thinks this might fit with other notification methods people are proposing. So does anyone else have any thoughts which would save me some thinking?
Yes - you can put your code in the TransactionReponse, there is a line
write after validation where everything is commited. 
We may want to set up an extention mechaism here, one entry before the
transaction (which validation could make use of), and one afterwards
(which notification and logs could make use of).
I wrote a horrible long, "Developers Notes" style review of the
TransactionResponse if you need a guide through the code...
Jody