Lazycoder

.NET Application server == null

Still about MS and enterprise systems. a post from discussion on channel9

Natty Gur posts about some of the shortcomings that .NET faces in the Enterprise. One of the first things I started to look for when I took on my latest task was a .NET version of JBoss, Gemstone or WebSphere. I couldn’t find any. It certainly looks like the pieces are there too build one using the .NET Framework, but none exist right now. I think we could build an application server that would outperform any Java app server.

Java application servers also come with naming services and proxies. Naming services are like UDDI they let the client get instant of class by the class name. in contrast with .Net that let us create instance from class just by referencing class assembly naming services let us get object from remote storage just by its name. This is very important service for enterprise systems where one component that one creates is used by all other systems.

You could hack something together using WS/.NET Remoting and the Activator but it still doesn’t handle the caching of the object, locks and so forth.

As I post earlier even MVC implementation of ASP.NET is an example for the difference attitude to enterprise development. While Microsoft published application block that implement MVC where the controller and the viewer are the same class Sun implements MVC with separate viewer and controller in their new development tool (that support now post back).

I’ve argued that the current ASP.NET code-behind model IS an MVC pattern and the View and the Controller do end up in different classes, but there are a lot of issues that go along with the implementation in ASP.NET. I’ve never figured out why they didn’t pattern it more after the JSP model. Afraid of being a copycat? More likely because they started spec-ing out ASP.NET before JSP was released. Plus, that MVC model is only for ASP.NET.