Hi,

First of all I love Microsoft tecnologies, realy, BUT not the prices... Certainly you understand... and my university and my enterprise think just like me.

Let get the point:
I've Apache source code and the Cassini too. I know I've got to develop a module to Apache (c++ :((() and I've to tranform the Cassini in a extra-module. First of all I wanna kown how can I access on .NET component from an non-.NET application so I can bridge the 2 worlds (APACHE-.NET).
2nd point is what is the procedure to implement an Application, Session and the requests. I mean, there is an object that I can create an manage the sessions and requests for him? For me the best thing is create an Application object and then just pass the requests form my bridge to my object in .NET. is that possible? If so... the object handles compilation, reads the global.asax file for himself?

Well... if anyone can help... I thanks for it.

PS: I'm portuguese so... forgive me my english and correct it if i've said some f*uck style word... :PP

It seems to me you don't need to do anything?

Apache can forward URL requests to an external web server, yes?

Cassini can handle those URL requests.

How's that?

May be you are right but... cassini only supports 1 application. So in an enterprise with more than one website it doesn't work. Can I install mutiple instances os cassini witch of them with one application?

Thanks for the post.

Cassini is not really recommended for production servers. It only support local requests by default and it's no supported on any basis to run smoothly on live servers on the internet... To support multiple apps you'll need to use work-arounds such as running cassini as a service (develop a Windows service with C# for example) which runs cassini on more than one port of the server. Then use the instance of the default port (80) to determine the request and send it to one of the other running instances on another port (such as /myapp redirect to port 8081 etc). But that's tricky business in fact.

Other idea, you can download the source of cassini and it's really possible to change the code to support more than just one application. You can for example add an .xml file to the directory which you want to be an application. If you determine this in cassini you can lauch another application'pool'. I refer to the cassini code to do this.

Have you checked out the mono project (http://www.go-mono.com). They have a mod_mono module for apache that might suit you.

Also, I believe that windows 2003 web edition is $300, which is a big saving from the old NT4/Windows2000 OS's, if you're just running websites. Its an attempt by microsoft to address the criticism of their webserver pricing.

Cathal

Hi ..

If you want some information about topic you've submitted you have to watch his site (in french):

http://www.dotnetguru.org/articles/DotNetFree/CassiniApache/ApacheASPNET.htm

I'm Italian then I could know a bit of french..

I wanto write C# webserver extending cassini then want to redistribute it open source.. like tomcat. If you want to join, we could open a new project open source..
For now I'm alone, and that is the topic for my Thesis.

Ciao: Patrik

Since Apache can forward a URL request then why don't you just use IIS? Or just IIS instead of Apache?

Wouldn't it be easier than porting Cassini to a service and making your own web server app?

 I use a commercial product for doing this, it is called the neokernel web server (from http://www.neokernel.com )

what about http://UltiDev.com/ ? I've heard quite few good things...

read this:

Cassini Web Server, as it’s distributed by UltiDev LLC, is based on code published at www.asp.net. However, to make Cassini truly useful and developer-friendly we added numerous powerful features, like:

• We made Cassini a windows service capable of running multiple ASP.NET applications simultaneously;
• Most important for Visual Studio developers, UltiDev Cassini can be easily included into your setup package. In Visual Studio 2005 UltiDev Cassini components are added as a Setup Prerequisites. In Visual Studio .NET 2003 Cassini is added as a custom Setup.exe bootstrapper for your MSI package.
• Applications distributed along with UltiDev Cassini can register themselves with the Cassini server after the installation - without you having to write a single line of code.
• We added Cassini Explorer - an ASP.NET application management user interface. Cassini Explorer is running under Cassini, of course;
• We added a very simple Cassini Configuration .NET API  for advanced application registration and configuration scenarios.

UltiDev Cassini Web Server comes in two flavors that are functionally equivalent, but target different versions of .NET Framework. Cassini 1.1 supports ASP.NET applications compiled for ASP.NET 1.0 and 1.1 and requires .NET Framework 1.1 to run. Cassini 2.0 supports applications compiled for ASP.NET 1.0, 1.1 and 2.0, and requires both .NET Framework 1.0 and 2.0 to be installed. The decision which one to use will be driven by what version of .NET Framework you expect your customers to have, as well as what version of ASP.NET your application was made for.

The remainder of this document is the set of detailed walkthroughs explaining how to make your ASP.NET application working with Cassini, how to debug with it, and how to create setup packages that bundle your ASP.NET application with UltiDev Cassini Web Server.