Hi. It seems to me that your needs are right on the scope of the WFS protocol. This protocol is in the vector-behavior sandbox, feel free to try it out and contribute to it. Protocol.WFS isn't in trunk yet, help to make it move forward will be appreciated. Thanks. Eric
2008/9/15, Björn Harrtell <[EMAIL PROTECTED]>: > Hi devs, > > I'm coding an application that uses OL vector editing and WFS transactions > quite heavily. > > I use a temporary OpenLayers.Layer.Vector for editing, moving stuff to a > OpenLayers.Layer.WFS as the user makes edits. This is a bit clumsy and > complicated but works. The reason why I'm doing this is because > OpenLayers.Layer.WFS only supports GET and is also loading features on > demand (hmm is this correct?) which doesn't fit my needs. Note that I do not > add the OpenLayers.Layer.WFS to a map, I only use create/commit the WFS > transactions. > > I would like to use something like a static/manually triggered WFS > (supporting POST and filtering) source to an OpenLayers.Layer.Vector that > syncs changes to the WFS source which then can be commited programmatically. > > Is this sort of what OpenLayers.Protocol.WFS (which I think is beeing worked > on?) is supposed to be used for? Or would it be sensible to make something > more of OpenLayers.Layer.WFS instead? > > Either way, I'm interested in (trying) to help out if this seems like > something you would like to support in OL, and can probably do it as a part > of the current project as it would simplify things for me I think. > > Regards, > > Björn Harrtell > GIS Consultant > SWECO Position > AB<http://www.swecogroup.com/en/Sweco-group/Services/Geographic-IT/> > _______________________________________________ Dev mailing list [email protected] http://openlayers.org/mailman/listinfo/dev
