|
Jimmy, Yes I was interested in attributes to be able to call WCF services (actually SOAP services) from Silverlight using Ruby. With WCF support, I think that IronRuby will become a huge catalyst for Silverlight, especially for web enterprise developers. At my work, SOAP services provide access to all our shared enterprise capabilities. All web apps use these services. Right now we use ASP.NET and are injecting more and more jQuery and JSON services to push the envelope on interactivity, richness and usability. I would rather use Silverlight but static languages are a drag on productivity for front-end development (don't get me wrong, I love C# for everything else - frameworks, services, etc.). So far, in prototypes, I have had to create C# wrappers on top of the WCF/SOAP proxies but that makes it even more brittle when we have to evolve our service signatures. I would love to simplify web development and have a consistent dynamic language experience on the browser side. IronRuby would be perfect in this scenario and would lower the bar for Silverlight development. A good example of course is what is being done around Gestalt. My perspective as an enterprise architect would be to include support for WCF in 1.0, but I totally understand the challenges of product scoping and shipping (I have experienced that for 5 years during the case tool years in the early nineties). The work so far on IronRuby is spectacular in my opinion both from a technical perspective as well as a from a collaboration and openness perspective! So keep it up! :-) Philippe Jimmy Schementi wrote:
|
_______________________________________________ Ironruby-core mailing list [email protected] http://rubyforge.org/mailman/listinfo/ironruby-core
