Hi Neal,

As long as your web service is accessible through HTTP GET, you should
be able to work with it using the _IG_Fetch...() API functions:
http://code.google.com/apis/gadgets/docs/legacy/remote-content.html#Fetch_XML

As the fetcher proxy caches the content, if you want your request to
hit your server web service every time, you will have to set the TTL
to 0, and possibly add a random parameter to the web service URL to
ensure uniqueness of each query.

If you need HTTP POST, you can already develop gadget in the iGoogle
sandbox and the new gadgets.io.* API, but there is currently no
timeline from Google to deploy the gadgets.io namespaced API with its
added functionalities to the iGoogle production environment.

I hope this helps.

Jerome

On Apr 15, 5:44 pm, Neal <[email protected]> wrote:
> I wrote my first XML/RPC web service yesterday, and today will attempt
> to call it from a gadget.
>
> But my question is:  If I have the luxury to write any type of PHP web
> service that I want, is there a specific type that works best or
> easier with Google Gadgets?   Any recommended code or models for
> this?
>
> So far, I've based my webservice on this 
> article:http://www.sitepoint.com/article/own-web-service-php-xml-rpc/
>
> I'm hoping for advice if I'm going down the path of best practices.
>
> Also, is there any good generic wrapper for MySQL to retrieve data
> from a query coded in a gadget.  In other words, a MySQL web service
> that I can just install (and maybe configure with some security on the
> server side), then call that from my gadget?
>
> Much Thanks,
> Neal Walters
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"iGoogle Developer Forum" 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-Gadgets-API?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to