The iSeries: The Once and Future King
Joe asked: "Okay, I'll need more education here. I have 20 people doing order entry simultaneously. They all need persistent connections, since this is an order entry application with lots of temporary data." Our web serving using WebSmart has ZERO persistant connections. We have a Purchase Order system written entirely in WebSmart. Up to 999 lines per purchase order, up to 99 comment lines per PO line. Works flawlessly. No persistance. Joe asked: " How many CGI jobs do I need for this? " We have more than 1,000 users using our websmart programs. There's never more than about 10 jobs running in QHTTPSVR to support these web pages users. Joe, I think some extended homework time is in order. You may be relying on stale knowledge about how CGI works. It may be time for you to bone up a little. Joe claimed: "It depends on what you mean by tool. An IDE such as the JDT in WDSC is fine (and indeed, almost mandatory). " From the time I click on the WSDc icon until I have a usable screen is over a minute. That's fine? (BTW, I've since removed WSDc from my PC as it is slow and a huge hog.) And, WSDc is not intuitive, it requires training. From the time I click on the WebSmart icon until it's in a usable state is 1.5 seconds. It gets better. From the time I select the option to create a new application that works like parent/child order entry application until the time I can excute the running application is approximately 5 minutes. I then have a working program that can be modified as necessary. Never a "blank page" syndrome. Joe asked: "How many CGI jobs do I need for this? If I only need five, where is the persistent session data stored?" In a WebSmart container called a Smurf. It's like a server side cookie which includes expiration. Joe, this is exactly what I've been saying. You condemn other solutions claiming that Java is the holy grail without knowing anything about the other solutions. It just reduces, dramatically, your credibility as a subject expert. And, that's unfortunate. It's also unfortunate that you have a podium from which to preach without fair and balanced knowledge of the subject matter. Joe asked: "How do you keep files open between calls?" They aren't, why would they be? Joe said: "you need to quickly dial down the rhetoric." Now you're being a comedian? chuck Opinions expressed are not necessarily those of my employer.
Joe asked: "Okay, I'll need more education here. I have 20 people doing order entry simultaneously. They all need persistent connections, since this is an order entry application with lots of temporary data." Our web serving using WebSmart has ZERO persistant connections. We have a Purchase Order system written entirely in WebSmart. Up to 999 lines per purchase order, up to 99 comment lines per PO line. Works flawlessly. No persistance. Joe asked: " How many CGI jobs do I need for this? " We have more than 1,000 users using our websmart programs. There's never more than about 10 jobs running in QHTTPSVR to support these web pages users. Joe, I think some extended homework time is in order. You may be relying on stale knowledge about how CGI works. It may be time for you to bone up a little. Joe claimed: "It depends on what you mean by tool. An IDE such as the JDT in WDSC is fine (and indeed, almost mandatory). " From the time I click on the WSDc icon until I have a usable screen is over a minute. That's fine? (BTW, I've since removed WSDc from my PC as it is slow and a huge hog.) And, WSDc is not intuitive, it requires training. From the time I click on the WebSmart icon until it's in a usable state is 1.5 seconds. It gets better. From the time I select the option to create a new application that works like parent/child order entry application until the time I can excute the running application is approximately 5 minutes. I then have a working program that can be modified as necessary. Never a "blank page" syndrome. Joe asked: "How many CGI jobs do I need for this? If I only need five, where is the persistent session data stored?" In a WebSmart container called a Smurf. It's like a server side cookie which includes expiration. Joe, this is exactly what I've been saying. You condemn other solutions claiming that Java is the holy grail without knowing anything about the other solutions. It just reduces, dramatically, your credibility as a subject expert. And, that's unfortunate. It's also unfortunate that you have a podium from which to preach without fair and balanced knowledge of the subject matter. Joe asked: "How do you keep files open between calls?" They aren't, why would they be? Joe said: "you need to quickly dial down the rhetoric." Now you're being a comedian? chuck Opinions expressed are not necessarily those of my employer.
Comment