What you are asking for is a syntax like: http://www.google.com/calendar?user=A?action=AddEvent?payload=string
correct? The Calendar API, as well as a lot of other Google APIs are based on the Google Data API protocol, which itself is based on the Atom Publishing and Syndication standard. That is the major thing distinguishing the URL parameter system from this - Atom Publishing is, by all means that matter, a documented and published standard. There are ton's of scenarios if you want to provide an API that are hard to solve (large payloads as an example) over the URL, which is one reason we have chosen the Atom protocol instead. The mime types are actually part of the standard as well and registered, so if you firewall does not support this, i would probably try to discuss this with your IT department (how do you guys read newsfeeds? A lot of them come down in that mimetype these days). To cut it brief, there is nothing we can do for you in that respect. Those parameters do not exist. Frank Mantek Google On Nov 19, 2007, at 2:14 AM, RioVic wrote: > > Philip, > > Thank you for the post, but it is just the same old documentation I > have been over for the last four days. I am so frustrated that my > head is going to explode. Look closely, those documents do not show > how to use a pure URL to add, delete or modify an event, they show > how to use an XML payload that requires an obscure MIME type which is > unsupported in my environment. > > Only calendar searches or "feeds", and the one documented pure URL to > add and event that I put in my previous post are documented as pure > URL's > > I have a hunch that this can (and should) all be done with pure URL > parameters. I wish someone at Google would explain to me where they > are. > > GRRRR! Going back to look at Exchange Server and their unpleasant but > powerful COM based API, slightly reworked for .NET, with much sorrow. > > RioVic > > On Nov 18, 3:50 pm, Philipp Kewisch <[EMAIL PROTECTED]> wrote: >> http://code.google.com/apis/calendar/developers_guide_protocol.html >> >> for direct interaction using HTTP methods (i.e in languages that >> don't >> have an api), or >> >> http://code.google.com/apis/calendar/developers_guide_js.html >> >> for browser-based javascript code. >> >> Philipp >> >> On Nov 18, 2:27 pm, RioVic <[EMAIL PROTECTED]> wrote: >> >> >> >>> All, >> >>> I would like to do calendar adds, updates and deletes directly form >>> the browser client, witout using the various libraries, JSON >>> formatting or XML. I found one documented example of how to do >>> this >>> here: >> >>> http://www.google.com/googlecalendar/event_publisher_guide_detail.html >> >>> The problem with the above is that it only covers the "add event" >>> functionality, not updates or deletes. I am looking for anyone who >>> has found further documentation on this method. It is a really cool >>> way to do things, since the browser handles your session >>> automatically, and you can easily put together the URL's using >>> javascript or similar scripting language. It truly "mashes up" the >>> Google calendar with your browser based application. >> >>> Thank you, >> >>> RioVIc- Hide quoted text - >> >> - Show quoted text - > --~--~---------~--~----~------------~-------~--~----~ > You received this message because you are subscribed to the Google > Groups "Google Calendar Data API" 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://group --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Calendar Data API" 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/google-calendar-help-dataapi?hl=en -~----------~----~----~----~------~----~------~--~---
