Re: [Cppcms-users] Some remarks

[Artyom <art...@ya...>]

> I tried it with nginx and apache2 and it did not work for both.

I've made a little test with root "/" with cppcms_run as is

- nginx worked but you should assume that path does not start with "/foo" but rather with "foo"
- apache didn't want to accept my rules but it looks like problem of configuration

Generally you should refer to the web server fast_cgi configuration to make service work from "/".

When CppCMS recieves a request it uses "PATH_INFO" CGI variable for matching the URLs so if 
PATH_INFO is provided correctly it should work.

Its a metter of correct web server configuration.

> The file delievery already works btw.

BTW CppCMS 1.x.x have its own internal web server and allows file hosting for development purposes only.

See:

http://cppcms.svn.sourceforge.net/viewvc/cppcms/framework/branches/refactoring/internal_file_server.h?revision=770&view=markup
http://cppcms.svn.sourceforge.net/viewvc/cppcms/framework/branches/refactoring/internal_file_server.cpp?revision=790&view=markup

It may give you some ideas how could this look like in next version. File Server itself is internal but it can be used as base for
such application.

In any case, serving files efficiently is **very** hard task, and I would recommend you relay on web server that can use functions like sendfile.
Or at least try to use features like X-Send-File header of lighttp and nginx. Because, be shure they do it better then you can write with best
cache.

> I have not used filters enough up to yet. But I am sure creating your own
> filters can be very handy.

Take a look on Wikipp it has "markdown" filter that is used for formattng pages. Also I 

> There is a telnet session at the end. Do you need other information?

As I send in previous mail. Thanks for the bug report. Fixed in trunk. 

> Ok, now I can't await CppCMS 1.x.x :-)

Me too ;)

Artyom.