Reply to thread

Message

Hi everyone,
I also thought about the architecture of the new web interface a long time. My idea of integrating the web server doesn't make sense anymore because of the TVServer.
My current ideas are very congruent with the diagram of Sam. Instead of cassini I would prefer: Hevea. Hevea is also an application server written in C# and licensed under GPL. It has more options than cassini and I think that it could be easier to integrate this in an own application.
I would prefer to write an own windows service which uses Hevea or cassini and not to use IIS to avoid problems (XP Home, installation etc.). The web application can be developed with IIS of course, but the whole web interface should be released as one package.

I have attached a small diagram of a possible architecture of such a windows service. I would like to help with the windows service, web service and my suggest abstraction layer.

Regards,
MisterD

<blockquote data-quote="misterd" data-source="post: 128740" data-attributes="member: 19503">Hi everyone,I also thought about the architecture of the new web interface a long time. My idea of integrating the web server doesn't make sense anymore because of the TVServer.My current ideas are very congruent with the diagram of Sam. Instead of cassini I would prefer: Hevea. Hevea is also an application server written in C# and licensed under GPL. It has more options than cassini and I think that it could be easier to integrate this in an own application.I would prefer to write an own windows service which uses Hevea or cassini and not to use IIS to avoid problems (XP Home, installation etc.). The web application can be developed with IIS of course, but the whole web interface should be released as one package.I have attached a small diagram of a possible architecture of such a windows service. I would like to help with the windows service, web service and my suggest abstraction layer.Regards,MisterD</blockquote>

[QUOTE="misterd, post: 128740, member: 19503"] Hi everyone, I also thought about the architecture of the new web interface a long time. My idea of integrating the web server doesn't make sense anymore because of the TVServer. My current ideas are very congruent with the diagram of Sam. Instead of cassini I would prefer: Hevea. Hevea is also an application server written in C# and licensed under GPL. It has more options than cassini and I think that it could be easier to integrate this in an own application. I would prefer to write an own windows service which uses Hevea or cassini and not to use IIS to avoid problems (XP Home, installation etc.). The web application can be developed with IIS of course, but the whole web interface should be released as one package. I have attached a small diagram of a possible architecture of such a windows service. I would like to help with the windows service, web service and my suggest abstraction layer. Regards, MisterD [/QUOTE]