>
> As others have pointed out, there is a difference if the result set is
> moderately big, for example 100 or 200 rows, versus when it is huge, for
> example the thousands or even millions of results you could get from a
> Google web search.  If the result set is huge, or may be huge, you
> pretty much have to break it into pages.  But if it is just moderately
> big my preference as a user is to see the whole thing in one scrolling
> page, rather than in several separate pages.  An example of the
> "moderately big" category is a shopping app where the most results a
> user could ever see is the number of items for sale at one web site,
> which is bounded.  See the search results in zappos.com.
>
> If the results are user-sortable, for example by clicking on a column
> header, then one big page also works better than several separate pages.



The question is if the scope is 200-500, does the live scrolling feature
still work well?

On search.live.com, you can use the scroll bar for the millions of search
results and the visible range is displayed to you ask you scroll.
http://search.live.com/images/results.aspx?q=msn&FORM=BIRE

In an enterprise web application where complicated business logics are
involved, can the data be presented fast enough?

- Cindy

    --------------------------------------------------------------
           Tip of the Day: Postings must be in plain text
     CHI-WEB: www.sigchi.org/web POSTINGS: mailto:[log in to unmask]
              MODERATORS: mailto:[log in to unmask]
       SUBSCRIPTION CHANGES & FAQ:  www.sigchi.org/web/faq.html
    --------------------------------------------------------------