On Fri, Oct 26, 2012 at 11:44 PM, Jeff Rogers dv...@diphi.com wrote:
Andrew Piskorski wrote:
On Fri, Oct 26, 2012 at 08:30:26PM +0100, Stephen Deasey wrote:
I was thinking it could work something like this:
- driver acquires lock, takes first conn thread off queue, releases lock
What if
Thanks, Stephen.
Finally I find I have to replace Ns_ConfigSection with Ns_ConfigGetSection.
Moreover, I have compiled the nsldap module and I am testing
Navisever in one cluster node. All Ok.
Regards,
Agustin
El 26/10/12 15:49, Stephen Deasey escribió:
On Wed, Oct 24, 2012 at 5:01 PM,
On 26.10.12 15:47, Stephen Deasey wrote:
I think the spec says that for HTTP/1.1, if the client doesn't
explicitly say to NOT send the body gzipped, say by using a q value of
0 (which we don't actually check for, woops...), then the server can
choose the encoding, although it should prefer the
On Sat, Oct 27, 2012 at 1:13 PM, Gustaf Neumann neum...@wu.ac.at wrote:
On 26.10.12 15:47, Stephen Deasey wrote:
I think the spec says that for HTTP/1.1, if the client doesn't
explicitly say to NOT send the body gzipped, say by using a q value of
0 (which we don't actually check for,
On 26.10.12 21:30, Stephen Deasey wrote:
I was thinking it could work something like this:
- driver acquires lock, takes first conn thread off queue, releases lock
- driver thread puts new socket in conn structure and the signals on
cond to that one thread (no locking, I don't think)
-
Agustin,
here is a port from nsldap_v0_r8 to the naviserver interface.
https://bitbucket.org/naviserver/nsldap/src
This should make it easier fro users to use this module...
-gustaf neumann
On 27.10.12 13:42, Agustin Lopez wrote:
Thanks, Stephen.
Finally I find I have to replace
the version on the tip handles now identity and q-values.
The logic sketched below does not handle cases, where e.g.
identiy or * is
higher than gzip qvalue, or explicit forbidding of gzip. The
values are doubles,
so one has to be careful with comparisons. I am not sure
about the logic for
