Re: Database Strategy - more...
This WebDNA talk-list message is from 1998
It keeps the original formatting.
numero = 18159
interpreted = N
texte = At 9:29 Uhr 10.06.1998, Marty Schmid wrote:(hotel reservation project)>1. What are people's thoughts on the feasability on such a solution?>>2. Is creating a single WebCat solution a better idea than coordinating>WebCat and FoxPro databases?Is it right that the decision for in-house FoxPro is fixed? In this casethe WebCat solution you mentioned does not eliminate the sync problem, youhave to sync foxbase and webcat anyway. If you want to be up to date at anytime then the inhouse database should write new or changed records astextfiles to disk and WebCat adds them to the existing ones every fewminutes or so. But - don't forget the deleted records - you will have towork out an update system with special syntax, based on the actions toperform, together with the other programmer (hopefully he is a nice guy...)>3. Can a WebCat-based solution handle the speed needs of approx. 40>full-time users (25 in-house, 15 or so on-line)?What means fulltime? Can you explain this in terms like number of queriesor hits per minute?I do not fear so much for WebCat, it runs still beside a webserver, so thespeed is limited and if you optimize performance (even with duplicated dataetc.) than it should run. But the 25 in-house users might bring the machineitself into troubles, if they are very active on a 10baseT or 100baseTnetwork they can easily lock the server up. Get a fast machine!Peter__________________________________________Peter Ostry - po@ostry.com - www.ostry.comOstry & Partner - Ostry Internet SolutionsAuhofstrasse 29 A-1130 Vienna Austriafon ++43-1-8777454 fax ++43-1-8777454-21
Associated Messages, from the most recent to the oldest:
At 9:29 Uhr 10.06.1998, Marty Schmid wrote:(hotel reservation project)>1. What are people's thoughts on the feasability on such a solution?>>2. Is creating a single WebCat solution a better idea than coordinating>WebCat and FoxPro databases?Is it right that the decision for in-house FoxPro is fixed? In this casethe WebCat solution you mentioned does not eliminate the sync problem, youhave to sync foxbase and webcat anyway. If you want to be up to date at anytime then the inhouse database should write new or changed records astextfiles to disk and WebCat adds them to the existing ones every fewminutes or so. But - don't forget the deleted records - you will have towork out an update system with special syntax, based on the actions toperform, together with the other programmer (hopefully he is a nice guy...)>3. Can a WebCat-based solution handle the speed needs of approx. 40>full-time users (25 in-house, 15 or so on-line)?What means fulltime? Can you explain this in terms like number of queriesor hits per minute?I do not fear so much for WebCat, it runs still beside a webserver, so thespeed is limited and if you optimize performance (even with duplicated dataetc.) than it should run. But the 25 in-house users might bring the machineitself into troubles, if they are very active on a 10baseT or 100baseTnetwork they can easily lock the server up. Get a fast machine!Peter__________________________________________Peter Ostry - po@ostry.com - www.ostry.comOstry & Partner - Ostry Internet SolutionsAuhofstrasse 29 A-1130 Vienna Austriafon ++43-1-8777454 fax ++43-1-8777454-21
Peter Ostry
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
Banner Ad example (Typhoon) and WebCatalog (1997)
Access Denied! But why? (1997)
Discount solution? (1998)
Almost a there but..bye bye NetCloak (1997)
Template Encryption (1998)
Progress Bar (2004)
CC Merchant suggestions?? (1997)
WebCat on Alpha? (1997)
Looping control (1997)
.htaccess to make WebDNA serve HTML (2007)
WebCat2 - [SendNews] (1997)
Sorting when searching with grouped fields (2002)
New Plug-in and Type 11 errors (1997)
problems with 2 tags (1997)
label?! (2005)
WebCatalog and barcodes (2000)
OLD ORDERS (1998)
carriage returns in data (1997)
WebCatalog and Webstar 3.02 (1998)
Multiple prices (1997)