Hello, list!
I never used geo-server, but I'm interested in its WFS-T functionalities.
If I set data source for a layer as WFS data (data from another map server with WFS support) and
a user of my server requests insert or update the features on that layer,
is that possible? If the user send those transaction requests sequentially,
can geo-server retain his or her previous transactions?
How does geo-server manage this kind of requests?
If you have some experiences with this, please let me know.
Thanks in advance!
from Myunghwa
myunghwa Hwang ha scritto:
Hello, list!
I never used geo-server, but I'm interested in its WFS-T functionalities.
If I set data source for a layer as WFS data (data from another map server with WFS support) and
a user of my server requests insert or update the features on that layer,
is that possible? If the user send those transaction requests sequentially,
can geo-server retain his or her previous transactions?
How does geo-server manage this kind of requests?
If you have some experiences with this, please let me know.
Thanks in advance!
The concept of transaction on multiple requests is not something we can support
as a database because HTTP is not a connection oriented protocol. We use long
lived locks instead.
We do implement the WFS 1.0 spec, you can read it in detail here:
http://www.opengeospatial.org/standards/wfs
The document is very detailed, a big long to read, but should give you answers
as well as example usages.
Cheers
Andrea Aime