Resending to avoid confusion….
One thing that seems to be missing in relation to X-OpenRosa-Version is what the request is for. I assume also that the different parts of the standard can be in different versions?
Or is that implicitly determined with the URL or having to actually read the first part of the payload? Having to ready the payload seems to be more than really needed to dispatch the request properly.
Best
Jørn
____________________________________________________________________________
Jorn Klungsoyr
openXdata - Centre for International Health, University of Bergen, Norway
www.openxdata.org / www.cih.uib.no / www.openrosa.org / www.open-mobile.org
Mobile: +4791365731, Skype/GoogleTalk: jornklung Alternative email: jorn.kl...@gmail.com
Post: Postboks 7800, 5020 Bergen, Visit: Årstadveien 21, 5th Floor, Bergen
------¤¤¤¤------
Thanx for clarifying, this is however not clear in the documents.
And this also requires a server to have multiple endpoints for something that really is not needed or read the first part of the payload to possibly know what to do about the payload (if using one URL for all).
I still think that the header should include what API and version, not just version, it would ensure that it could be used regardless of what URL is being used (the same or different).
And would ensure the server would know exactly what context this is in, just from the header.
Best
Jørn
____________________________________________________________________________
Jorn Klungsoyr
openXdata - Centre for International Health, University of Bergen, Norway
www.openxdata.org / www.cih.uib.no / www.openrosa.org / www.open-mobile.org
Mobile: +4791365731, Skype/GoogleTalk: jornklung Alternative email: jorn.kl...@gmail.com
Post: Postboks 7800, 5020 Bergen, Visit: Årstadveien 21, 5th Floor, Bergen
------¤¤¤¤------
i'm pretty sure multiple endpoints is how every other web app does
stuff like this.
i also don't know what you mean by the header should include the api.
you want a header with x-openrosa-api:formlist?
yaw