Seriously.
Most applications need a client-side component, be it: ActiveX, Silverlight, or Flash. Simply because the browser is only intended to display HTML and execute Javascript. Yes, that's not all and I'm being a bit reductive. That's why I'm interested to see what HTML5 can do and further browser support for it.
Anyways, back to the project.
Why am I not using WCF? Don't get me wrong. It'd be very good if I were to use WCF and learn about it. But I'm sure I'll run back into WCF again. I want to write my own polling mechanism in Silverlight. I just think it'd be more interesting. A lot of what we're building should be modular. Anyways, it's not that big of a deal. If I'm building a web service and I get a WSDL generated (I'm NOT writing it myself, I've done that before ...); then .NET will generate a proxy anyways.
I'm still under technical investigation. I have to research how to build a web service using Ruby on Rails. My main concern is that Ruby on Rails is very high. You use ORMs mainly to manage your database. I need my web service/access to be multi-threaded and all that jazz. I'm sure I can get the control I want. Just want to know how.
Also, I have to think about how to run both Ruby and .NET on the same machine. Since there's no way in hell I'm using mono. That means I'll be booting into my windows environment. Since I don't have a good desktop and I have a shitty MBP ... I can't use VMs.
This is going to be interesting. Anyways, time to research Ruby.
No comments:
Post a Comment