Thanks, I have already started looking at the documentation, and its not as intuitive as I had hoped. I believe to understand the concept, such as the actual file format and protocol. I am having difficulty in grasping the HTTP portion.
For example, I believe the actual premise of HTTP as it relates to this discussion, is that it's a type of protocol that allows to; POST, PUT, GET and DELETE requests. It's the implementation of HTTP that I do not understand. For example, 1. Apply for Google Base Authentication Key. 2. Create a .xml Atom 1.0 product feed that conforms to Google Base elements/attributes. How to I "push" and/or "request" via HTTP for product feed sent of picked up? Is it a special program like ftp, etc...? Thanks, JC On Mar 11, 5:27 pm, Celebird <[email protected]> wrote: > (1) circumvention and automation, yes; > i wouldn't say "real-time" -- especially > with respect to the products item-type. > > (2) similar -- but they are not the same; > for some api's there's no xml involved -- > however, the underlying stored-data is xml. > > (3) it depends on which client-api is used and how. > for batch-inserts yes -- you might store a file > containing a series of xml batch-inserts; other > client-api's use function-calls to insert items > without files; all the api's use http. > > (4) i would start with a set of requirements and this > link:http://code.google.com/apis/base/index.html --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Base 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-Base-data-API?hl=en -~----------~----~----~----~------~----~------~--~---
