<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/"><channel><title>Karsten Januszewski on 'myspace'</title><description>Karsten Januszewski blog posts filtered by a specific tag</description><link>/irhetoric/blog/tags/myspace/default.aspx</link><language>en-us</language><pubDate>Fri, 21 Nov 2008 12:32:19 GMT</pubDate><generator>Oxite</generator><item><title>MySpace Developer Platform</title><description>&lt;p&gt;The &lt;a href="http://developer.myspace.com/community/" target="_blank"&gt;MySpace Developer Platform&lt;/a&gt; is now online, sort of.&amp;#160; Hats off to these guys for shipping, although at this time, you can only play by invite only, which they are hand picking, &lt;a href="http://developer.myspace.com/Community/blogs/devteam/archive/2008/02/06/registered-now-what.aspx" target="_blank"&gt;according to their blog&lt;/a&gt;.&amp;#160; The other slightly frustrating thing is that, at this time, if you do manage to get a key, and you do manage to write an application, you have to invite others to be able to see it, &lt;a href="http://developer.myspace.com/Community/blogs/devteam/archive/2008/02/05/let-me-see-my-app.aspx" target="_blank"&gt;as explained here&lt;/a&gt;. The interesting model in this case is that you have to actually log into MySpace &lt;em&gt;as the application &lt;/em&gt;in order to grant others the right to use your application.&amp;#160; All of this is subject to change once the platform matures, but it makes things a little rough at first.&amp;#160; I just want to get on the whitelist!&lt;/p&gt;  &lt;p&gt;They have a REST API and there's already &lt;a href="http://developer.myspace.com/Community/forums/t/144.aspx" target="_blank"&gt;a good thread&lt;/a&gt; going in the forums on writing a .NET Client library for it.&amp;#160; Interested?&amp;#160; Come join the thread.&lt;/p&gt;  &lt;p&gt;Another interesting thing to note is, on the server side, they've implemented this using Windows Communication Foundation, which &lt;a href="http://blogs.msdn.com/vbertocci/archive/2008/01/31/wcf-and-myspace-a-restful-mix-session.aspx" target="_blank"&gt;they'll be talking about at Mix&lt;/a&gt;.&amp;#160; My goal: bring some client WinFX goodness to the party ;). &lt;/p&gt;  &lt;p&gt;Makes me wonder what kind of WCF client could be written for these services.&amp;#160; There is the [WebGet] attribute.&amp;#160; So, I suppose, you'd grab the XML from the REST service and infer schema from it and then pass that to SvcUtil to generate a proxy. Should work.&amp;#160; I guess the question is how much elegance/productivity/performance one gains by using WCF on the client for a REST service.&lt;/p&gt;  &lt;p&gt;Sidenote: too many .NET wrappers out there seem to roll there own serialization.&amp;#160; There's such great baked in support in the framework for XML Serialization that I'd love to see the emerging MySpace .NET client take advantage of it, whether through WCF or not.&amp;#160; The other option would be to look at the work done in the Google .NET client library, which is factored so elegantly and has a rockin ATOM parser.&amp;#160; It still isn't entirely clear to me how much of the MySpace data is formatted as ATOM data.&lt;/p&gt;  &lt;p&gt;&lt;img src="http://b2.ac-images.myspacecdn.com/00000/20/52/2502_m.jpg" /&gt;&lt;/p&gt;</description><comments>http://www.rhizohm.net//irhetoric/blog/39/default.aspx</comments><link>http://www.rhizohm.net//irhetoric/blog/39/default.aspx</link><pubDate>Thu, 07 Feb 2008 15:08:00 GMT</pubDate><guid isPermaLink="true">http://www.rhizohm.net//irhetoric/blog/39/default.aspx</guid><dc:creator>Karsten Januszewski</dc:creator><slash:comments>0</slash:comments><trackback:ping>http://www.rhizohm.net//irhetoric/blog/39/trackback/default.aspx</trackback:ping><category>Mix08</category><category>MySpace</category><category>Web 2.0</category></item></channel></rss>