I am checking the examples of WAA.
If to the DBF CUSTOMER I go adding lines, the navigator every time slow more 
time for to see the BROWSE.
Right now the number of lines is of 5.000, instead of the 70 that it comes 
with the installation.
Does it mean this that WAA is not worth for great quantity of data?.
I don't know that it would happen if I had to install an application with 
databases of 100.000 lines or more.
Do I have to make a browse that doesn't visualize all the data of a single 
time?.
The test is making it in my small domestic net.
If we proved it in internet, the time of wait would be still bigger.
That I can make?
Thanks.

On Sat, 15 Oct 2005 14:45:41 +0200, César Calvo wrote:

> Does it mean this that WAA is not worth for great quantity of data?.

If you are trying to display all the data at once - yes. But that is true
for any type of server backend processing. The additional problem with
the internet is that you do not have guaranteed response times.

> Do I have to make a browse that doesn't visualize all the data of a single
> time?.

Yes. Take a look at Ebay - result sets there are only 20 or 50 articles -
at the top and bottom of the page there are navigational controls to get
the next/previous/first/last page(s).

Thomas

César,

> Does it mean this that WAA is not worth for great quantity of data?.
> I don't know that it would happen if I had to install an application with 
> databases of 100.000 lines or more.

No, the problem is one of tuning.  The code assumes a small set of data,
which has grown disproportionatly.  In practice, you would write code that
collates only a subset of the data and generates small pages to be returned
to the client.  As Thomas said, eBay displays only a few items at a time,
and the response is very good.  Try and display everything an it will take
time to fetch all that data from the database, time to collate/translate
that into a web page, and time to transfer that to the client.

Here at Compucar, we have a database consisting of over 14000 tables and
over 1Gb of data (without digging into history files!) and yet our WAA apps
have a turn-around time of around 0.08 secs per page.

> Do I have to make a browse that doesn't visualize all the data of a single 
> time?.

To be honest, you must do this unless you can guarantee that your data
will never grow.

WAA is fast!

Phil Ide

*******************************************
*   Xbase++ FAQ, Libraries and Sources:   *
*   goto: http://www.idep.org.uk/xbase    *
* --------------------------------------- *
* www.xodc.org.uk - openSource Dev-Center *
*******************************************

I'm not a complete idiot - several parts are missing.