#10923 closed (fixed)
Use thread-safe GEOS API if available
| Reported by: | andrew_pendleton | Owned by: | jbronn |
|---|---|---|---|
| Component: | GIS | Version: | dev |
| Severity: | Keywords: | geos thread safe safety | |
| Cc: | Triage Stage: | Accepted | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
The number of configurations under which GeoDjango can be used is limited by its relative lack of thread-safety as compared to the rest of the framework, mainly due to the lack of thread-safety of underlying libraries like GEOS. The latest release of GEOS adds a thread-safe C API (proposed in http://trac.osgeo.org/geos/wiki/RFC3, tracked in http://trac.osgeo.org/geos/ticket/210, and committed prior to the release of GEOS 3.1.0), so GeoDjango should use it if it's available.
Attachments (3)
Change History (8)
comment:1 by , 17 years ago
| Keywords: | geos thread safe safety added |
|---|---|
| milestone: | → 1.2 |
| Owner: | changed from to |
comment:2 by , 17 years ago
comment:3 by , 16 years ago
| Triage Stage: | Unreviewed → Accepted |
|---|
by , 16 years ago
| Attachment: | geos_threadsafe_v1.diff added |
|---|
by , 16 years ago
| Attachment: | geos_threadsafe_v2.diff added |
|---|
threading.local subclasses and I/O function accessors are actually necessary
by , 16 years ago
| Attachment: | geos_threadsafe_v3.diff added |
|---|
Improved comments, and a few imports over last patch.
comment:4 by , 16 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
See also the GeoDjango mercurial branch for a thread-safe GEOS interface. Thanks to a dev known as tazle, we have a beginning implementation, however, it's a non-trivial addition that can benefit from additional testing.