[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: (ITS#6504) Corrupted control value when using pagedresults with subordinate *ldap* database

Le 05/04/2010 23:40, masarati@aero.polimi.it a écrit :
>>> Well, I've just fixed it.  When changing database, I modified the paged
>>> results control value by setting the page size to pagesize -
>>> rs->sr_nentries, with an empty cookie.  I'll commit tomorrow, as now I
>>> only have http access.
>> Speedy patch - thank you! Just tried it out, and it works great for the
>> issue I reported.
>> Testing further shows a limitation in crossing databases though. A
>> search that spans over two glued ldap databases, returns n<  pagesize
>> results from the first, and continues over to the second, returning
>> pagesize-n results from it, making pagesize results all together. So
>> far, so good.
>> However, the subsequent search with the returned pagedresults cookie
>> just starts a new search over, returning the same set of results. So it
>> works fine for one page max.
>> But it doesn't look simple to solve this issue, unless backglue starts
>> recording pagedresults cookies, etc...
>> Anyway, great improvement on not sending back free'd cookie :-)
> I see the issue, and it seems to be not related to my patch.  Don't know
> how to fix it (yet).  It'll probably need a separate ITS.

No, I don't think it is related to your patch. However, it has just 
appeared, as a result of going one hurdle further thanks to your patch :)

I see you opened a separate ITS in #6507. I'll followup there.
Jonathan Clarke - jonathan@phillipoux.net
Ldap Synchronization Connector (LSC) - http://lsc-project.org