Hi Tamás,
I'm not aware of any issues in particular with search results, however
JX struggles a little with large numbers of entries in the user interface.
I've worked with it on databases with 100,000+ entries and when there are
over ~20,000 entire *actually displayed* in the tree view it can get quite
slow.
*However* the search function is independent of the client; it's a
vanilla ldap search which is evaluated by the server. If the search
returns large numbers of entries (e.g. 20,000+) it may slow down a fair
bit; a partial solution is to give JX more memory in the start up script,
but a better solution is to ask why you're using a graphical tool to browse
20,000+ entries; normally a more refined search is more useful :-).
There are other limits to the ldap search protocol you should be aware
of; most servers have a 'search limit' for a particular query, JX allows
you to set paged results that will work through large data sets by
repeatedly querying the server.
- Chris
On 22 March 2013 21:51, Tamás Kálmán X <tamas.x.kal...@ericsson.com> wrote:
> hi CHris
>
>
>
> I heard that there exists an issue with jxplorer. if the ldap database is
> too large and its structure is ackward, then the search function may fail
> and not all the results may be displayed. i have checked the JXv 3.2
> documentation on the website with this regard, however i could not find any
> reference to this issue/limitation.
>
> does a later version of this user guide exist mentioning this limitation?
>
>
>
> many thanks
>
> tamas
>
--
Dr Christopher Betts
Pegacat Software
Melbourne, Australia
m: 0408 533 456
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar
_______________________________________________
Jxplorer-users mailing list
Jxplorer-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jxplorer-users
