[Lazarus] New application type: HTTP standalone server

[ABorka]

>
>
> On Fri, 3 Jun 2011, ABorka wrote:
>
>>>> On 6/2/2011 10:46, Leonardo M. Ramé wrote:
>>>>> Michael, I added a webmodule to testhttp and got two problems.
>>>>>
>>>>> 1 - Could not determine HTTP module for request "". Even if I call it
>>>>> the same way as I use with fpCGI and fpEmbWeb.
>>>>
>>>> This error usually happens when the project main program does not have
>>>> the webmodule unit in it's uses statement.
>>>
>>> I managed to reproduce the error; The error is only apparent if there
>>> are
>>> multiple modules registered. I committed a fix in 17647.
>>>
>>> This raises the question again of the FPWeb behaviour for
>>>
>>> http://somehost/path
>>>
>>> Now, 'Path' is interpreted as the name of the action for the default
>>> module.
>>>
>>> For an embedded server, this is not logical. This should be the module
>>> name, not the action name.
>>>
>>> Michael.
>>
>> I disagree. The vast majority of web applications do not need multiple
>> web
>> modules (usually the default module is used), but they use multiple
>> actions.
>> Therefore, action names should have priority over module names if only
>> one of
>> them is passed.
>
> Hm. My experience is very different:
> I didn't make a web application yet that had a single module.
> All had at least 3 or 4... And they're all in production.
>
> Except some demo applications for FPC, they usually have 1  :-)
>
> Maybe we should introduce 'TWebHandler.PreferModuleName : Boolean', which
> is
> False by default.

And you do not specify the actions in the URLs when multiple web modules
are in your application? I think actions are always specified when web
modules are in the calling URL. But it is not true the other way around.

AB