Difference between revisions of "fcl-web"

From Lazarus wiki
(document why the fastcgi, custfcgi, and fpfcgi units are not supported on Darwin)
Line 1: Line 1:
= Notes =
+
{{Web and Networking Programming}}
 +
 
 +
== Using fpWeb together with Lazarus ==
 +
 
 +
===Installing the fpWeb Lazarus Package===
 +
 
 +
The first step to do is installing the package which comes in the path lazarus/components/fpweb/weblaz.lpg
 +
 
 +
===Creating your first application===
 +
 
 +
A very simple web application which displays an html page can be ...
 +
 
 +
===Deploying this very simple application===
 +
 
 +
===Reading GET fields===
 +
 
 +
== Notes ==
  
 
The cgiapp unit is deprecated, please use fpcgi as much as possible.
 
The cgiapp unit is deprecated, please use fpcgi as much as possible.
  
 
The fastcgi, custfcgi, and fpfcgi units are not supported on Darwin at this time, because it uses a different mechanism than the MSG_NOSIGNAL option for recv() to indicate that no SIGPIPE should be raised in case the connection breaks. See http://lists.apple.com/archives/macnetworkprog/2002/Dec/msg00091.html for how this should be fixed.
 
The fastcgi, custfcgi, and fpfcgi units are not supported on Darwin at this time, because it uses a different mechanism than the MSG_NOSIGNAL option for recv() to indicate that no SIGPIPE should be raised in case the connection breaks. See http://lists.apple.com/archives/macnetworkprog/2002/Dec/msg00091.html for how this should be fixed.

Revision as of 21:49, 13 July 2010

Template:Web and Networking Programming

Using fpWeb together with Lazarus

Installing the fpWeb Lazarus Package

The first step to do is installing the package which comes in the path lazarus/components/fpweb/weblaz.lpg

Creating your first application

A very simple web application which displays an html page can be ...

Deploying this very simple application

Reading GET fields

Notes

The cgiapp unit is deprecated, please use fpcgi as much as possible.

The fastcgi, custfcgi, and fpfcgi units are not supported on Darwin at this time, because it uses a different mechanism than the MSG_NOSIGNAL option for recv() to indicate that no SIGPIPE should be raised in case the connection breaks. See http://lists.apple.com/archives/macnetworkprog/2002/Dec/msg00091.html for how this should be fixed.