GBPVR Web

[CodeMonkey]

Thanks for the input mamema. That would certainly be a possibility with what I was proposing. The .NET executables I was proposing could run from any (assuming the server would run .NET executables) web server, not just the one in gbpvr. As part of the internal servers configuration, you could configure if you want to run the server at all, and what port you wanted to use.

[sub]

Quote[/b] (mamema @ April 17 2004,08:49)]i like this web server stuff a lot, but consider the following:

the whole htpc stuff is in its early stages. The most people which using this kind of stuff are technical skilled people, so the one button install solution isn't necessary at the moment (perhaps at a later time)
Because there are some technical skilled people out there, these kind of people might have already a webserver (like myself). Then i install a tool like gbvr and have another webserver?
Then i need another port for the new webserver.....
Then i have problems to connect because some companies block other ports than 80 or 21
Then the webserver gets useless to me.....

This kind of solution is suitable to every kind of tool i've installed on the PC which has a webserver included.

Because of that i would prefer a solution where i can point gbvr to a directory where the files are stored but where these files will be used from my webserver (apache)

Perhaps a second solution is if the user is able to choose if he wants to use the build in gbvr webserver or an external webserver

By the way: IIS is a webserver with a lot stuff included. And it needs a lot configuration skills to lock down these security holes.....
I think using IIS for gbvr is like throwing weapons of mass destruction on a car thief  

regards

mamema

Hi mamemam,

The way I see it, there is enough web server technologies that whatever I pick, someone is going to think I should have used something else (IIS/Apache/ASP.NET/PHP/CGI/same machine/different machine/etc).

In the situation you describe, you could do the following. Run the GB-PVR webserver on a non-standard web server port (e.g. 7886), and configure apache to do a proxy pass if it gets a request matching a particular pattern "/GBPVR/.*". Any requests that apache receives for http://myapacheserver/GBPVR/index.html etc would be passed to the right server with apache acting as the middle man. This would also support apache web server serving from another machine.

The components I'm talking about using arn't actually IIS (I said this to simplify my answer), but are the ASP.NET System.Web.Hosting APIs. These are one of the core piece used by IIS and other webservers that support ASP.NET. This would not be a heavy weight implementation.
If you want to know more about this approach, look for a project on the net called Cassini.

Using this approach also may let you disable the built in server, and install IIS or Apache (with asp.net support) and point it at the specific directory.

[gplasky]

I took a look at the Cassini project. Very cool. I think this would be the way to go. And like you said if you included something similar to Cassini it could be disabled and a full blown web server could be still be used.

Gerry

[mamema]

@sub

thanks, i know the mod_proxy and mod_rewrite stuff can do that. The only thing to consider is, that Microsoft has implemented IIS "only" stuff which other web servers can't handle.
That is the cause for my posting. Several products are IIS-based so it won't even work on apache or whatever.....
Proxypass or Reverseproxy won't help you out in every situation were IIS stuff needs to be forwarded to another webserver and port

So as long as the implementation of the web stuff isn't "microsoft-only" (let's say: stuff which only IIS can handle) based, i'm happy with it.

regards

mamema