Just an update: After we changed our server side to no longer return (the valid!) return code 201 after the initial POST request created an entry, but instead return 200, our test app started working. We are able to run a full round trip via POST + PUT request. URI remains stable, ETAG gets updated --> just as expected.
This puts Orkut back in the lead (hi5 gets the POST done, but fails with the PUT, it is coming in as a POST; myspace is not even able to send the PUT and complains that the etag is missing). Too bad that 3 containers have such different implementations. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Orkut Developer Forum" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/opensocial-orkut?hl=en -~----------~----~----~----~------~----~------~--~---
