Not using Web Server for html pages

For an intranet application instead of using a proper web server, it has been planned to just deploy static html pages by sharing it ove开发者_如何学编程r the network. This static html page is continously updated in the background by a program running on that PC and people access this html page by typing the shared file path directly in the browser. A maximum of 10 simultaneous users are expected to access it. Can any one see the disadvantages or advantages in this type of deployment?

The problem is that this is what Web server side programming languages are designed to solve. One disadvantage is that this makes the process overly complicated. Web servers can be pretty light weight if the issue is not wanting extra administrative overhead. It sounds like you'd be writing a lot of data unnecessarily. I'd suggest using some Web based programming language/platform like PHP, Perl, ASP.NET, etc to just serve up content.