Look like there's a great example here:
http://google-data-api.blogspot.com/2008/05/clientlogin-with-php-curl.html

Make sure to change the service to 'gbase'.

There's also a shell script here that may help:
http://gdatatips.blogspot.com/search/label/ClientLogin

Eric

On Sep 10, 11:26 pm, Sridevi <[EMAIL PROTECTED]> wrote:
> The example is in zend framework. i want to write programatic login using
> curl. please help me.
>
> Thanks,
> sridevi.
>
> On Thu, Sep 11, 2008 at 2:29 AM, Eric (Google) <[EMAIL PROTECTED]> wrote:
>
> > Hi there,
>
> > AuthSub and OAuth are the best authentication methods
> > for web applications because they don't expose a user's credentials
> > to your application.  Instead, users are sent to Google to authorize
> > access to their data.
>
> > Once you have a session token, just use that for subsequent requests.
> > The user only has to authenticate once.
>
> > In the Recipe Application, the long-lived session token is stored in
> > a $_SESSION variable:
> >http://code.google.com/apis/base/phpdevguide.html#authentication
>
> > Eric
>
> > On Sep 10, 10:22 am, sridevi <[EMAIL PROTECTED]> wrote:
> > > I am using curl . please give me any sample code of programmati
> > > c login
>
> > > On Sep 10, 10:20 pm, sridevi <[EMAIL PROTECTED]> wrote:
>
> > > > Hi,
>
> > > > I have run the recipe application given in php to insert items into
> > > > google base successfully.
> > > > But i need to run the program without logging in into gmail account
> > > > everytime.
> > > > Is there any way to write the programatic login functionality? If any
> > > > examples are there please provide them.
>
> > > > Thanks,
> > > > Sridevi.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to