Opps! Re: Recommendation - That's 200-400 users per day
----- Original Message ----- From: "Bob Campbell" <rcam@psouth.net> To: <Zope@zope.org> Sent: Friday, October 05, 2001 7:58 PM Subject: Recommendation?
Hi, We have a group developing a web-based application using mySQL as the backend and Zope as the "frontend." The app contains 16 forms, lot's of writes, and few reads. The forms contain 5-16 fields. The app requires minimal security. We are running Zope 2.4 on NT.
We are looking for general advice on any procedures or processes that are routinely used for this type of a form based application.
Thanks Bob Campbell Banknorth Financial Inc. 207-761-8595
Subject: Re: [Zope] Opps! Re: Recommendation - That's 200-400 users per day We are looking for general advice on any procedures or processes that are routinely used for this type of a form based application. Hi Bob,
Can you be more specific?
Cheers,
- C
Hi Chris, Absolutely. Some background: Building data driven web applications is a new (ad)venture for many of our business line developers. Most are used to desktop applications built with Access and VB. A few have taken the Zope course taught by Michael Pelletier. The application being built is a fairly complex loan input system. Most of the application will follow a step by step sequence through a series of forms. There is no existing data. All of the data is completely generated by the user. The users will input dozens of fields with information through the first 2-3 forms and then part of that information will be queried and visible in many of the other forms. With the amount of fields and forms, the application is slow. Very slow. All of the coding is done with ZSQL methods and dtml. The database is in mySQL and set up as an ODBC data source. I have the following questions (Note: I am not a programmer. I'm a designer*. I know just what I have to know about programming languages and building applications. I am far more comfortable with CSS, HTML, DHTML, site architecture and learning ZPT. I am also one of technical advisors for the Intranet, which is why I'm writing this and not the programmers.) 1. I've setup ZMySQLDA, tested it and it works. Would there be a significant difference using ZMySQLDA rather then ODBC? 2. A number of people have asked me about session tracking and caching. I don't know enough about either one to give an intelligent answer. Are they applicable in this type of situation? *Each form will open in a chromeless window with buttons directing the user, the context menu will be disabled so it is unlikely the user will go "back." Any tips or advice would be greatly appreciated. Thanks, Bob
On Sat, 2001-10-06 at 17:17, Bob Campbell wrote:
Can you be more specific?
The application being built is a fairly complex loan input system. Most of the application will follow a step by step sequence through a series of forms. There is no existing data. All of the data is completely generated by the user. The users will input dozens of fields with information through the first 2-3 forms and then part of that information will be queried and visible in many of the other forms. With the amount of fields and forms, the application is slow. Very slow. All of the coding is done with ZSQL methods and dtml. The database is in mySQL and set up as an ODBC data source.
Hmm. So you are collecting the data from the user, storing it in an RDBMS, and then querying that same data to generate subsequent forms? What do you do with the data at the end of this proccess? What do you do with this data if the application is abandoned at various stages?
2. A number of people have asked me about session tracking and caching. I don't know enough about either one to give an intelligent answer. Are they applicable in this type of situation?
Absolutely, if I understand your situation correctly. Storing the interim data in a session object will keep it in RAM as long as the user session continues. If at the end of the application proccess you need to store the info (or some subset of it) in an RDBMS, you should be able to do that with a single RDBMS transaction. This will have the effect of increasing the performance of your application, as it eliminates the unneccessary storing and retreiving of data in the RDBMS. HTH, Michael Bernstein.
participants (3)
-
Bob Campbell -
Chris McDonough -
Michael R. Bernstein