-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I was thinking that it might by interresting to implement a read/write lock
system to work with the global_dns_cache, using the mutexes and the mutex
functions. By using this will restrict API users to give only a simple mutex
system, they will not be able to make their own system. But when I check the
source code, it will be difficult to create their own locking system
(read/write or something like that), without complexifying all our API
functions. It will complexify because we will be obliged to tell then when we
are writing, reading, or other things like that.

We need to decide if the sharing API we offer must be used by the users just
to give us the possibility to get the best of it, or let the user the most
flexibility, but adding more complexity to the API, because at this time it's
not possible with the current API design to get the possibility for the user
to create his oen read/write mechanism.

- --
Jean-Philippe Barrette-LaPierre
Maintener of curlpp: When TRYING(but still in good way) to get the best of C++
(http://www.sourceforge.net/projects/curlpp)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE+GdSxb/24YeGNKWQRAunHAJ9cnCdqTDfjAJ9ZQA4N4NKpprzB5QCdGUu1
vxM69pV5pc25qng4jUy+AF4=
=NcyM
-----END PGP SIGNATURE-----

-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
Received on 2003-01-06