I am actually interested in the Java client library. The use case is to take an end-user-visible URL from the "wild" (for example, someone IMs me a URL they cut-and-pasted from their browser window) and confidently obtain a canonical structure that enables use of the actual gdata API (or client library) to get the metadata associated with that URL.
For example, a Picasaweb album can be referenced in multiple ways via a "slideshow" URL, normal URL, possibly with authkey query parameters, etc. There are also some kinds of URLs that redirect the browse to the actual object. All these things make it inconvenient to reliably scrape out the relevant bits that can be used to construct even the initial API call. At an even higher level, some factory method could, given an arbitrary URL, return the appropriate API family that would provide further details (e.g., Picasa vs. Youtube), or even say that this is not a Google-service URL at all, which would provide a nicer mechanism than having to scrape the URL for different domain names, then follow path components and query keys. On Thu, May 29, 2008 at 9:16 PM, Frank Mantek <[EMAIL PROTECTED]> wrote: > > The .NET library actually has some of that ability. You can pass a URL > into a query object and the query object parses that URL into it's > query components. It is not going to give you some of the other > breakdowns (the path parts). Is that the functionality you are looking > for? > > I was actually considering retiring this for the future, as i have not > seen any use for it, and it does not work in the compact framework.... > > Frank Mantek > Google > > On May 30, 2008, at 5:52 AM, Robert Tsai wrote: > > > > > There do not appear to be any client library interfaces that, given a > > URL (e.g., to a youtube video, picasa album, picasa photo, picasa > > slideshow, etc.), return some kind of canonicalized structure that > > contains everything required to use some GData API to get that same > > referenced content in a structured way. > > > > The URLs so far are easily "scrape-able" to get what is needed (for > > example, http://picasaweb.google.com/userid/albumname/ > > photo#s<photoid>, > > but it would be nice to have an "authoritative" way to get this > > information. Strictly speaking this is not really a GData API thing, > > but a client library thing. > > > > Can these kind of "factory" interfaces be considered for some future > > GData client library release? The developers at Youtube, Picasa, etc. > > are the ones most familiar with the various flavors of URLs that could > > be floating around and best suited to provide this kind of mechanism. > > > > Thanks, > > --Rob > > > > > > > > -- Robert Tsai | [EMAIL PROTECTED] | http://www.xoopit.com/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Data Protocol" 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-help-dataapi?hl=en -~----------~----~----~----~------~----~------~--~---
