> 1) OpenLDAP client API ({dr}ecent versions) should not suffer of any
> buffer overflow.
It sounds good.
> 2) asynchronous vs. synchronous should not be a choice here, as soon as
> your application can start handling data as soon as it comes in, without
> waiting for the search response.
>
> 3) on what basis you suspect that OpenLDAP might suffer from buffer
> overflows while you seem to be so confident that the supermagicsecret
> commercial server you plan to use won't.
I never said the commercial server does so magic things. I wanted to
clarify about the openLDAP client, because it is the 'client' which stores
the big results till it is completely delivered by the server. Here, there
is no overhead at the server, but only at the openLDAP client.
Earlier I suspected whether the openLDAP client might have some big
hardcoded buffer size, which I thought may not be bigger enough for my
usecase. But, if you confirm that there are no such problems at the
openLDAP client, I will go ahead with the synchronous request.
---
You are currently subscribed to [EMAIL PROTECTED] as: [EMAIL PROTECTED]
To unsubscribe send email to [EMAIL PROTECTED] with the word UNSUBSCRIBE as the
SUBJECT of the message.
