you need an application that can send data using http.
no -- ftp can send data-feed-files but ftp and
data-feed-files have little to do with the api.
the item-type determines what data to send,
what attributes and values are required per-item,
and the data's format.
google's protocol determines what request to send,
what url and http methods are required per-command,
and the request's format.
one reason the api's exist is to hide details --
such as what xml to send or how to send http.
the google-base-data api client-libraries send xml using http.
each client-library has api calls for authenticating,
inserting, updating, deleting, and searching for items;
they send both the command-requests and item-type data.
there's a lot of xml under-the-hood --
so be careful which xml in which context.
e.g.
- xml item-type data (attributes and values).
- xml requests sent for authentication,
insert, delete, update, query and the
xml returned for each.
- xml-batch commands.
- xml data-feed-files for upload --
which have little to do with the api;
if you want to send the raw-xml requests and item-type data
then almost any application that can send data using http
should do -- e.g. curl, php.
because http/rest is such a common protocol, knowing the
details helps when using methods other than google api's
or for application design and debugging.
i believe it's a good thing to understand that there
are xml and http details -- if for no other reasons
than creating better solutions and better debugging;
but, the api's can hide many if not all of these details.
###
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
