There appears to be more than one failure condition here. Aside from the
extremely slow execution when the test succeeds, I still see infinite
hangs occurring.
My latest run from last night is still running now, and slapd.3.log
shows there is a msgID in Request Completed state that has been
At 11:06 AM 10/7/2005, Howard Chu wrote:
There appears to be more than one failure condition here. Aside from the
extremely slow execution when the test succeeds, I still see infinite hangs
occurring.
My latest run from last night is still running now, and slapd.3.log shows
there is a msgID in
Howard Chu writes:
On the other hand, when exactly is it possible for a single request to
have more than one result message?
SearchResultEntry/Reference and the newer IntermediateResponse. I
seem to remember there was an extended search result or something once
which was removed due to lack of
Kurt D. Zeilenga wrote:
At 11:06 AM 10/7/2005, Howard Chu wrote:
On the other hand, when exactly is it possible for a single request to have
more than one result message?
In LDAP, there can be many intermediate responses (as in a search
entries, search references, and extended
At 02:09 PM 10/7/2005, Howard Chu wrote:
Kurt D. Zeilenga wrote:
At 11:06 AM 10/7/2005, Howard Chu wrote:
On the other hand, when exactly is it possible for a single request to have
more than one result message?
In LDAP, there can be many intermediate responses (as in a search
entries,
Kurt D. Zeilenga wrote:
And in ldap_parse_result in libldap/error.c, as I've already pointed out, we
queue responses with their originating requests. Any LDAP Request can only have
one Result message, regardless of how many intermediate messages may be
included. So it appears that all
At 02:47 PM 10/7/2005, Howard Chu wrote:
Kurt D. Zeilenga wrote:
And in ldap_parse_result in libldap/error.c, as I've already pointed out, we
queue responses with their originating requests. Any LDAP Request can only
have one Result message, regardless of how many intermediate messages may be
Kurt D. Zeilenga writes:
What about the case where ldap_result(3) is called for any and
all? The message chained returned could contain responses
from multiple requests.
ldap_result() should return responses to one specific request.
ldap_result(,msgid=LDAP_RES_ANY,,) may pick any outstanding
At 04:23 PM 10/7/2005, Hallvard B Furuseth wrote:
Kurt D. Zeilenga writes:
What about the case where ldap_result(3) is called for any and
all? The message chained returned could contain responses
from multiple requests.
ldap_result() should return responses to one specific request.
After
Given that ldap_result() returns only responses from a
single operation (or a single unsolicited response), I
figure that 'results' in LDAP_MORE_RESULTS_TO_RETURN must
have referred to responses, that is searchResultEntry,
SearchResultReference, SearchResultDone.
That is, it would seem reasonable
10 matches
Mail list logo
