Ticket #252 (closed task: fixed)
[DS] Look into using FastCGI
Reported by: | astephen | Owned by: | lawrence |
---|---|---|---|
Priority: | desirable | Milestone: | BETA |
Component: | community | Version: | |
Keywords: | DataExtractor GeoSPlAT | Cc: |
Description
Investigate use of FastCGI for CGI interface.
Change History
comment:2 Changed 15 years ago by astephen
- Summary changed from Can we use FastCGI to [DS] Can we use FastCGI
comment:4 Changed 15 years ago by astephen
- Type changed from issue to task
- Summary changed from [DS] Can we use FastCGI to [DS] Look into using FastCGI
comment:5 Changed 15 years ago by lawrence
- Milestone changed from BETA to PreBeta
I've done some initial looking into this, and will talk with Andrew H about it after GO-ESSP ...
comment:6 Changed 14 years ago by astephen
- Status changed from assigned to closed
- Resolution set to duplicate
Bryan looking into this and other frameworks so close.
comment:7 Changed 14 years ago by lawrence
- Status changed from closed to reopened
- Component changed from T03_DataExtractor to T10_Working_Grid
- Resolution duplicate deleted
- Milestone changed from PreBeta to BETA
comment:8 Changed 14 years ago by lawrence
- Owner changed from astephen to lawrence
- Status changed from reopened to new
reopened so it doesn't get lost ... but it is my problem now.
comment:10 Changed 14 years ago by lawrence
I've now done quite a bit of investigation into this: see my "whither our web servers series": parts pone, two, and three.
I've followed this up with a real installation of fastcgi in lighttpd on my laptop, see details of how that was done at installing lighttpd and fastcgi.
The next step will be to play more thoroughly with wsgi, and potentially put the discovery engine within it.
comment:11 Changed 14 years ago by lawrence
- Status changed from assigned to closed
- Resolution set to fixed
fastcgi is a considerable improvement on other options. If we are only doing python in fastcgi we might consider scgi as preferable, but at some future time.