I should have mentioned that the app will only be used on a LAN based 
environment for an inhouse order entry system.

bandwidth is not the issue, 100 meg ethernet between all the clients and 
the server.

I'm just cautious that when they go from 1000 products, 300 suppliers and 
3600 customers to numbers 10x that size (which is likely within the next 
year) that these screens will start to really bog down...

of course I've tried to limit the point of taking this big hit by doing 
things like telling them if the customer pre-exists in the system, look 
them up first and create an order from a screen that will at least 
pre-populate the customer field info... this takes one chunk out of the 
render process, but i still have 1000 products and suppliers to deal with.

;)

I was thinking of maybe trying to start analyzing which data is rarely 
used, and start moving that to an archived state... thus reducing the 
amount of data that has to be loaded each and every time.

has anyone done anything like this? could be a good use of creating a 
turbine scheduled job to peruse the data and mark off things which haven't 
been sold in the past two years to just being archived...



On Thu, 29 May 2003, Lester Ward wrote:

> > I guess the real limitation is the clients physical ram and if you 
> > can wait long enough for the browser to parse such big files.
> 
> Seems to me that you should be more concerned with user experience than with
> the server technology. Browse your site using a 56k modem and rate the
> experience. If it is less than good, the issue is the amount of data you are
> sending down the pipe, not the server's ability to generate it. My gut tells
> me that an 800k HTML file == not the best user experience, but perhaps it
> makes sense for your site.
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to