Hi,

Our TOS and Program Policy do not allow download of the client-side
API or the visualizations. You need to use the API as it was meant to
be used - over the cloud.

We just released (today) the wire protocol to allow anyone to create
server-side implementations of data sources that connect to
Visualization compliant visualizations, charts, etc. However, you may
not download the visualizations onto your servers.

You raise several concerns relating to SaaS, Google platforms and
Google Visualization API and I'll try to address these:

Google believes in the web as the new computing platform. We believe
that SaaS can be provided reliably, efficiently, affordably and with
many added benefits to users, be they private or commercial /
businesses. By chance, I writing this today after having attended
Dreamforce - Salesforce.com's annual conference - this morning, where
thousands of commercial businesses (from SMBs to Fortune500
companies), all basing critical components of their business on SaaS,
met and discussed how to further this model even more. This is not the
proper place to take this general discussion further - but you get my
point - the tools we provide are for the cloud.

Google Platforms for SaaS are mature and continue to improve literally
on a daily basis. As you may know, this has become a significant
offering at Google and considerable resources are placed into making
these systems, services and APIs robust, scalable and dependable.
Recently, for example, the GMail team announced four-nines up-time for
GMail on Google Apps and Google provides SLAs for the premium version
of Google Apps.

As for backward and "forward" compatibility - I can share with you
that we are working towards guaranteeing long-term support for all our
APIs. I cannot disclose details yet, but I can share with you that it
will be multi-year support. You can safely assume that our current
protocol version will be supported for a long time.

You will certainly be able to continue using older versions of the
client for quite a while prior to upgrading to newer versions and you
do have to worry about us puling the plug on the API. We currently do
not support versioning for the visualizations themselves, but we will
place this as a feature request on our list and see if it makes sense.

As for availability of Google's servers - I've commented on that
generally above. We have high availability, we are working to make it
even better and premium versions enjoy even higher availability. Most
companies' IT department's server availability is not as high as what
Google provides. In any case this is a strategic decision you have to
make, as did all the companies running on Salesforce. Amazon's
platform, Google's AppEngine, etc.


On Nov 3, 3:42 pm, Ashwath Murthy <[EMAIL PROTECTED]> wrote:
> Bumping this again. Any answers to this? I'm faced with a similar
> situation..
>
> On Oct 2, 5:31 am, "[EMAIL PROTECTED]"
>
> <[EMAIL PROTECTED]> wrote:
> > Thanks for the response, trollswagen.  I understand that there's
> > nothing stopping me from being able todownloadthe source of the
> > entire API from a technical standpoint (though it may require a number
> > of changes if the URLs are not relative).  Really, the question is
> > whether or not we are allowed to do it legally.  They have not
> > released it under an open source license such as Mozilla, BSD, LGPL,
> > etc.  The fact that they don't have the package available fordownload
> > (or a link to the CVS / SVN) concerns me.  The license is somewhat
> > unclear, and I want to make sure that we are permitted to do it before
> > investing in development.
>
> > Thanks again!
>
> > Cheers,
> > Christopher
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google Visualization 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-visualization-api?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to