[
https://issues.apache.org/jira/browse/DIRSERVER-1212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12623643#action_12623643
]
Emmanuel Lecharny commented on DIRSERVER-1212:
----------------------------------------------
Well, for the time limit, you are right : it's far more complex than I expected
it to be.
Now, what if we check the time while validating an entry, instead of doing so
while returning an entry? I'm not sure it's necessary to add a new cancel
method, or to create two new overloaded methods, time aware. A simple check, if
the time limit is set, should do the trick.
The idea is to avoid having a thread to manage the time.
Another question you raised is related to the abandonRequest : we should be
able to 'kill' the current request immediatly. This could be done in the same
place we check for the time limit.
Still a bit blur, but we can use this thread to discuss the options.
> Size time limits on SearchControls broken in core-jndi
> ------------------------------------------------------
>
> Key: DIRSERVER-1212
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1212
> Project: Directory ApacheDS
> Issue Type: Bug
> Components: core
> Reporter: Alex Karasulu
> Assignee: Alex Karasulu
> Priority: Blocker
> Fix For: 1.5.4
>
>
> I commented out some tests in SearchIT.java in core-integ that rely on the
> correct operation of search size and time limits through paramters in a
> SearchControls object. This is not working any longer. Fix it and remove
> @Ignore tags.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
