> It seems that session management create one separate session by each module
That's right but should be OK, as the session is created based on cookie,
which if already exists, will be loaded instead of created. If memory serves
right, I remember you should set one or a few of these:
* fphttp.Sess
El 21/03/18 a les 16:32, Luca Olivetti ha escrit:
I have a standalone web application (fphttpapp) with a main module and a
couple of additional modules.
I developed it a while ago with fpc-2.6.4 and it works quite well.
If I compile it with fpc 3.0.4 it stops working:
Never mind, meanwhile I
I have a standalone web application (fphttpapp) with a main module and a
couple of additional modules.
I developed it a while ago with fpc-2.6.4 and it works quite well.
If I compile it with fpc 3.0.4 it stops working:
1) the second time I load a page I get an error
Error: Duplicate name: A co
On Tue, 20 Mar 2018, Anthony Walter wrote:
Okay, but the problem with the current implementation in Classes.pas is
that Status cannot be used, Terminated cannot be checked, and there is no
access to Synchronize.
All wrong. See below.
As such OnStatus is pointless, and the semantics of
chec
