[Mapserver-dev] Re: mappool.c thoughts

[Frank Warmerdam]

Sean Gillies wrote:
  > I think it's a good thing that our functions require just the bare minimum
> context.  Passing a connection pool everywhere would suck.  I'm happy with
> your proposed solution, with one additional suggestion.
> 
> Let's consider adding a
> 
>   ConnectionPool *connectionpool
> 
> member to layerObj.  If NULL, we use the default module-level pool.  In the
> mapscript case, it would reference an application-level pool.  Calls to
> the msConnPool functions could be passed self->connectionpool.

Sean,

Sure, that sounds fine.  I try to work on this in the next couple weeks.

Best regards,
-- 
---------------------------------------+--------------------------------------
I set the clouds in motion - turn up   | Frank Warmerdam, warmerdam at pobox.com
light and sound - activate the windows | http://pobox.com/~warmerdam
and watch the world go round - Rush    | Geospatial Programmer for Rent