On Jan 26, 5:00 pm, Rossko <[email protected]> wrote: > I don't think > [you must not] > 10.8 use the Static Maps API other than in an implementation in a > web browser; > sits very easily with the proposed use of static maps in a server to > construct a PDF to be fed to a browser. That doesn't seem to me to > be the same as the end-user using his browser to 'print' a screenshot > to PDF or whatever.
I don't think providing the software necessary to produce a PDF server- side is really different from having that capability on the client machine (for these purposes). After all, Google is all about cloud computing--this is something like that. Most people using Windows don't know how to print to PDF unless they bought Acrobat. Adobe likes it that way--that's why Microsoft is prohibited from including the functionality in Windows. This solution would just make it easy for them. Heck, there could even be a link saying "Print this page to PDF." If the terms care about where the software required for functionality lies, that rules out using dumb terminals. I don't think that is the purpose of the terms. Of course, a judge could decide I'm wrong in this interpretation. Though I doubt this would ever get to a judge--if Google doesn't like this implementation they can just update the terms to specifically rule it out at any time. -Brian -- You received this message because you are subscribed to the Google Groups "Google Maps 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-maps-api?hl=en.
