The requironments for the U action is just a individual entry update e.g. an update to an specific existing entry ID like http://www.yourdomain.com/gdata-server/feedID/someIDb9832a35012704c7bc8cc3326997d9a611f116e7 you could also have a look at http://code.google.com/apis/gdata/protocol.html
simon On 6/6/06, Chuck Williams <[EMAIL PROTECTED]> wrote:
Simon, What are your U requirements in the CRUD? Are these only on individual items so that delete/add is sufficient, or do you have any bulk update requirements? Chuck Simon Willnauer wrote on 06/06/2006 05:47 AM: > Hello, > > the first version of the GDATA server is already running and it > supports all > the CRUD actions base on a lucene storage. > so the next thing is to enable multiple feed ( I wouldn't be a proper > server > serving just one single feed instance :). > Basically the gdata - protocol description doesn't say anything about > inserting new feed instances, the API neither. > Lot's of possibilities are around to create an interface for inserting > new > feeds. XML descriptors per feed could be possible but that could easily > become a xml nightmare. So what else could be provided... There could > be a > SOAP endpoint for creating/deleteing new Feeds or a secondary REST - > Based > Interface could be provided. This feeds could be stored inside the > storage > component including user account data (should we provide more than one > user > account for altering feeds?!). Quiet easy to use would be a > administration > JSP based component of the server, but guys don't forget I just have 2 > 1/2 > month time ;). No problem doing all these extra features when SoC has > finished. > --> I thought about a mySQL connector for storing entries and requesting > feeds in addition to the lucene base storage and BerkleyDB as well. > > regards Simon > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
