On Mon, 2011-05-23 at 22:47 -0400, Lee Jenkins wrote: > On 5/23/2011 9:29 PM, ABorka wrote: > >> What is the typical strategy to server up static content with fpWeb? JS, > >> css files, given that its handler centric. > >> > >> Create a default handler that checks for file extension in the .PathInfo? > >> > >> -- > >> Warm Regards, > >> > >> Lee > > > > Why would you need fpweb to serve static content? Your web server does that. > > CGI/FCGI and apache modules (fpweb) are to generate dynamic content. > > > > AB > > > > Good question. I want to deploy as an embedded server without the need to > install apache, etc for small workgroups and so the I need to allow the > server > to server up a few key files which could be from the file system or embedded > in > the executable file for instance. > > For the most part the static files that I'd like to server up are the > index.html > page (entry point) and it's dependent script and or css files. All of the > other > html content will be served up through the templating system and injected > into > the initial index.html page through ajax or constructed client-side as a > result > of JSON data received from the server as well. I figured instead of writing > separate web modules/actions for each...
I still do not understand why you didn't use 'fppkg install embweb' and used that. That embedded webserver does all you want. Joost. -- My Lazarus blog: http://www.lazarussupport.com/lazarus/weblog -- _______________________________________________ Lazarus mailing list [email protected] http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
