I would also be interested to understand why " paged results is inherently flawed".

-----Original Message----- From: John Unsworth [mailto:john.unsworth@cp.net] Sent: 17 September 2013 12:07 To: 'Pierangelo Masarati' Cc: 'openldap-its@openldap.org' Subject: RE: (ITS#7698) Multiple Paged search requests on one connection fail

Thank you for your reply.

...

Technically speaking, paged results consists of perfectly independent operations from the protocol point of view

Yes but the results have not all been retrieved - only the first page full - and further operations are needed to get the additional results. Hence paged searches are not really independent but are linked by the cookie. The results are supposed to remain available so that additional searches using the same cookie can retrieve them. Every other LDAP server I have come across allows multiple concurrent paged searches on a single connection.

The RFC does seem to allow the OpenLDAP behaviour but it seems extremely restrictive to me. It should at least be well documented.

-----Original Message----- From: Pierangelo Masarati [mailto:pierangelo.masarati@polimi.it] <snip> No, it's correct (at least, that's the intended behavior). The operation structure is only persistent for the duration of the operation, whereas the connection structure persists for the duration of the connection. Technically speaking, paged results consists of perfectly independent operations from the protocol point of view, so persistent state is saved in the connection structure. Of course, multiple cookies could be stored, but since paged results is inherently flawed, it was decided to handle it this way. Clients need to use a dedicated connection for search operations that use the paged results control.

p.

-- Pierangelo Masarati Associate Professor Dipartimento di Scienze e Tecnologie Aerospaziali Politecnico di Milano