#10923: Use thread-safe GEOS API if available ------------------------------+--------------------------------------------- Reporter: andrew_pendleton | Owner: nobody Status: new | Milestone: Component: GIS | Version: SVN Keywords: | Stage: Unreviewed Has_patch: 0 | ------------------------------+--------------------------------------------- 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.
-- Ticket URL: <http://code.djangoproject.com/ticket/10923> Django <http://code.djangoproject.com/> The Web framework for perfectionists with deadlines. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django updates" group. To post to this group, send email to django-updates@googlegroups.com To unsubscribe from this group, send email to django-updates+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-updates?hl=en -~----------~----~----~----~------~----~------~--~---
