Is ActiveWebService anywhere near ready?
I have to say that most of the grief I've had with getting Rails up and running satisfactorily has been to do with ActiveWebService. The problems below about marshalling booleans and converting UUIDs to strings have only occurred when marshalling over SOAP. Likewise, now I have FastCGI up and working, it's only the web-service (scaffold and invocation) that fails.
We also have an ASP.NET2 front end calling a Rails back-end service (running on WEBrick). I was hoping that this could be my show-piece service, detailing how fast it will be to get back-end services written. But even in WEBrick, the ASP service keeps getting a "connection was unexpectedly closed by server" message. I'm looking at rewriting the service in .NET (using the excellent, light-weight ASP.NET WebMatrix tool). Yes, I know it's only .NET 1.1 but it's quick, easy and runs quickly on older machines (sadly not on my Mac).
I will return to Rails Web Services at some point, but in the interests of getting some work done, I need to switch to ASP for now. I'm a bit narked about this to tell you the truth. However, I'm pleased to say that my traditional web-sites, written using Rails, IIS and SQL Server are all fine.
No comments:
Post a Comment