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 > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
