Zend Framework

GData only allow POST as request method and not PUT

Details

  • Type: Improvement Improvement
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Not an Issue
  • Affects Version/s: 0.6.0, 0.7.0, 0.8.0, 0.9.0
  • Fix Version/s: 0.6.0
  • Component/s: Zend_Gdata
  • Labels:
    None

Description

Google API expect specific method for each action.
To create a new entry in blogger you have to use POST (HTTP), but if you want to modify this entry, you have to use PUT.

GData only allow post so you can't modify an entry for example in Blogger.
This also affect the new Picasa API as you have to use PUT to update a photo.

This should affect other Google API.

The DELETE (HTTP) should also be allowed.

Proposal:
Maybe the HTTP method should be an attribute of the method post of the class Zend_Gdata (and maybe the method post should be renamed)

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Darby Felton added a comment -

Assigning to Bill Karwin.

Show
Darby Felton added a comment - Assigning to Bill Karwin.
Hide
Permalink
Ryan Boyd added a comment -

The GData component does allow for modifying an entry via retrieving an individual entry, updating it, and then calling the save() method on it. The same thing is true of the delete() method. (These two are located in Zend_Feed_EntryAtom).

It may be desirable to have a method put() and delete() in the Zend_Gdata class which takes an entry and calls the put or delete method on it-- but this would only be for convenience and uniformity, and would not add functionality. As the delete method would not require anything beyond the edit URL for an entry, it could acceept either just the edit URL or an EntryAtom as params.

-Ryan

Show
Ryan Boyd added a comment - The GData component does allow for modifying an entry via retrieving an individual entry, updating it, and then calling the save() method on it. The same thing is true of the delete() method. (These two are located in Zend_Feed_EntryAtom). It may be desirable to have a method put() and delete() in the Zend_Gdata class which takes an entry and calls the put or delete method on it-- but this would only be for convenience and uniformity, and would not add functionality. As the delete method would not require anything beyond the edit URL for an entry, it could acceept either just the edit URL or an EntryAtom as params. -Ryan
Hide
Permalink
Ryan Boyd added a comment -

Zend_Gdata has always supported updates to entries. Updating the entry object and performing $entry->save() updates the entry on the server by performing a HTTP PUT operation. $entry->delete deletes the entry from the server by performing a HTTP DELETE operation.

As of ZF 1.0PR1, Zend_Gdata_App (which each service inherits from) also supports performing the updates/deletes by passing an entry and/or URL.

Show
Ryan Boyd added a comment - Zend_Gdata has always supported updates to entries. Updating the entry object and performing $entry->save() updates the entry on the server by performing a HTTP PUT operation. $entry->delete deletes the entry from the server by performing a HTTP DELETE operation. As of ZF 1.0PR1, Zend_Gdata_App (which each service inherits from) also supports performing the updates/deletes by passing an entry and/or URL.

People

Vote (0)
Watch (2)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Zend Framework. Try JIRA - bug tracking software for your team.