Re: [google-appengine] Support for HTTP Patch in URLFetch
Hi Nick,
You should probably send this to google-appengine-python@ instead, then.
>
Thanks - given that I've start this here, I'll finish it here. (I did look
for the appengine
python list, but could not find it easily - could I suggest that a pointer
to the group be
put in the welcome and readme for this group?)
> I'm doing some work using the Salesforce REST API. This API uses the HTTP
>> Patch
>> command to update an object in SF. I note that URLFetch currently does not
>> support
>> Patch - any plans to support in future?
>>
>
> PATCH is actually a part of WebDav, not HTTP. If you'd like support for it
> added to urlfetch, you should file a feature request on the issue tracker.
>
I'm a little confused - Salesforce does refer to it as a HTTP command and
this RFC
http://tools.ietf.org/html/rfc5789
does give the impression that it is part of HTTP rather than Webdav. Any
chance you'd
be able to shed further light on this?
> I think the solution is to use httplib2 - it's a bit clunky, however.
>>
>
> Unfortunately, I don't believe this will work - httplib is just a wrapper
> for URLFetch, so any restrictions that apply to URLFetch apply equally to
> httplib(2).
>
This can work using the following (which I got from some SF examples):
queryConn = httplib2.Http()
resp,content = queryConn.request( obj_url+'?_HttpMethod=PATCH',
"POST",
headers= {'Authorization': 'OAuth
'+access_token, 'Content-Type':' application/json'},
body=simplejson.dumps(update_fields) )
I have not looked into what happens under the hood, however...
BR,
Seán.
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/google-appengine/-/XSp99pCaBh4J.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-appengine?hl=en.
[google-appengine] Support for HTTP Patch in URLFetch
Hi, Issue for GAE-python. I'm doing some work using the Salesforce REST API. This API uses the HTTP Patch command to update an object in SF. I note that URLFetch currently does not support Patch - any plans to support in future? I think the solution is to use httplib2 - it's a bit clunky, however. Thoughts/comments appreciated. BR, Seán. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/bnDsbTzsfYgJ. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
[google-appengine] OpenID consumer application
Hi, I'm trying to do some work with openid - I don't want to use the federated login as I also want to support facebook connect. (I'm open to advice on the best approach to do this, but for now, I've been looking into rolling my own openid functionality). I've been looking at the example provided here: http://code.google.com/p/google-app-engine-samples/downloads/detail?name=openid-consumer_20080704.tar.gz However, I'm having some issues with it. First off, I can't seem to get it working at all and I've done a bit of digging inside the code to figure out what is going on - the behaviour seems a bit strange and not what I would expect in appengine. More specifically, I see the following issues: - before going off to a provide to authenticate, information pertaining to the session is generated and it looks like it should be written to the datastore (in store_session() ) -- however, the information is not written to the datastore as the first char in the dynamic property is '_' --- this relates to the '_openid_consumer_last_token' field of the session specifically -- related to this, the type of the object associated with the above is an openid.consumer.discover.OpenIDServiceEndpoint which cannot be written to the datastore in its current format This is giving rise to some other problems for me as when I get the callback, it is not straightforward to find the endpoint and check the authentication (in the complete() phase). I could make some mods to json up the endpoint class and I think this might solve the problem, but I was wondering more generally whether there are good reasons not to do this and indeed why the appengine variant operates as it does. Any comments/pointers appreciated. BR, Seán. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/BQ8PFwgugssJ. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
