Comments on: Introducing LiveInfo.. http://www.nodetraveller.com/blog/javascript/introducing-liveinfo/ Another blog about someone playing about with web development Sat, 06 Sep 2008 20:57:34 +0000 http://wordpress.org/?v=2.6-bleeding By: Lawrence http://www.nodetraveller.com/blog/javascript/introducing-liveinfo/#comment-85 Lawrence Mon, 21 Feb 2005 10:50:29 +0000 http://www.nodetraveller.com/blog/?p=31#comment-85 You can manage the maximum number of results returned by coding in the server side plugins. You could use a hidden field to denote the maxminum number of results you want returned and let the server cut it off. Also there is a threshold limit on the text fields which is redefinable. The default is 3 so searching for "A" would be impossible but "the" might return large results set. You can manage the maximum number of results returned by coding in the server side plugins. You could use a hidden field to denote the maxminum number of results you want returned and let the server cut it off.

Also there is a threshold limit on the text fields which is redefinable. The default is 3 so searching for “A” would be impossible but “the” might return large results set.

]]> By: Kendall Willets http://www.nodetraveller.com/blog/javascript/introducing-liveinfo/#comment-78 Kendall Willets Sun, 20 Feb 2005 19:14:16 +0000 http://www.nodetraveller.com/blog/?p=31#comment-78 The problem I have with pre-fetching is that the results of searching for "A" or some other short string are too numerous. If it could talk to the server and ask for results 11-20, etc., it would save a lot of overhead. It wouldn't hurt to cache somewhat more than what's displayed, say results 1-100, but it needs some cutoff before it gets the whole set. The problem I have with pre-fetching is that the results of searching for “A” or some other short string are too numerous. If it could talk to the server and ask for results 11-20, etc., it would save a lot of overhead.

It wouldn’t hurt to cache somewhat more than what’s displayed, say results 1-100, but it needs some cutoff before it gets the whole set.

]]> By: Lawrence http://www.nodetraveller.com/blog/javascript/introducing-liveinfo/#comment-68 Lawrence Thu, 17 Feb 2005 10:46:37 +0000 http://www.nodetraveller.com/blog/?p=31#comment-68 It gets all the results and just displays one page at a time. The results are in a list with all the list items set to display none except for those on the current page. It gets all the results and just displays one page at a time. The results are in a list with all the list items set to display none except for those on the current page.

]]> By: Kendall Willets http://www.nodetraveller.com/blog/javascript/introducing-liveinfo/#comment-66 Kendall Willets Thu, 17 Feb 2005 05:02:23 +0000 http://www.nodetraveller.com/blog/?p=31#comment-66 Nice work. I would have commented earlier, but I'm still digesting the documentation. I like the result scrolling -- does it send a new query for each scroll, or cache the whole result set? Nice work. I would have commented earlier, but I’m still digesting the documentation.

I like the result scrolling — does it send a new query for each scroll, or cache the whole result set?

]]>