The iSeries: The Once and Future King
I don't think there's anything to find fault with in any event. But that aside, does CGI require the memory of Java for JSP? No, we all know it could be written in C as far as that goes. The job overhead? I have a pending question about that, but I thought I saw many moons ago something about CGI job overhead being taken care of by IBM. I don't know. That's why I'm asking. But it's hard to believe that a job is still spawned for CGI to create a web page, unless IBM just deliberately wants to cripple non-Java Websphere SQL solutions, which I wouldn't put past the dudes in Armonk. We all know the Sys/3X only exists as it is because Rochester told Armonk they were building an accounting machine. As for DoS, it would seem to me to be brain dead to have socket code that is allowed to tie up the AS/400 responding to DoS attacks. Sure, it will deny service of legitimate web accesses mixed in there, but the job allocation for servicing sockets ports should just dwindle until the attack dissipates. I do understand the "we don't want our crown jewell exposed to the internet" thinking, sorta, as far as port 80 goes I guess is what they have in mind. Still, it should be a smaller AS/400 with DDM communications to the crown jewell AS/400's, although only an OS/400 knowledgeable person will believe that. I think PC's are used because web people in most corporations are not AS/400 people and they require their OS to run on a PC, not because the PC is cheap. That's just an excuse that justifies corporate behavior in deference to their web people who don't give a rat's behind for the AS/400 and how OS/400 can kick their butts six ways to Sunday. For that matter, IBM doesn't have a clue about it either. Just look at their i5 ads. They really think they're going to sell i5's to consolidate those cheap PC's from those people I was talking about. Give me a break. It's integration within OS/400, not outside of OS/400, that sells the AS/400. But only Rochester would know that. rd
I don't think there's anything to find fault with in any event. But that aside, does CGI require the memory of Java for JSP? No, we all know it could be written in C as far as that goes. The job overhead? I have a pending question about that, but I thought I saw many moons ago something about CGI job overhead being taken care of by IBM. I don't know. That's why I'm asking. But it's hard to believe that a job is still spawned for CGI to create a web page, unless IBM just deliberately wants to cripple non-Java Websphere SQL solutions, which I wouldn't put past the dudes in Armonk. We all know the Sys/3X only exists as it is because Rochester told Armonk they were building an accounting machine. As for DoS, it would seem to me to be brain dead to have socket code that is allowed to tie up the AS/400 responding to DoS attacks. Sure, it will deny service of legitimate web accesses mixed in there, but the job allocation for servicing sockets ports should just dwindle until the attack dissipates. I do understand the "we don't want our crown jewell exposed to the internet" thinking, sorta, as far as port 80 goes I guess is what they have in mind. Still, it should be a smaller AS/400 with DDM communications to the crown jewell AS/400's, although only an OS/400 knowledgeable person will believe that. I think PC's are used because web people in most corporations are not AS/400 people and they require their OS to run on a PC, not because the PC is cheap. That's just an excuse that justifies corporate behavior in deference to their web people who don't give a rat's behind for the AS/400 and how OS/400 can kick their butts six ways to Sunday. For that matter, IBM doesn't have a clue about it either. Just look at their i5 ads. They really think they're going to sell i5's to consolidate those cheap PC's from those people I was talking about. Give me a break. It's integration within OS/400, not outside of OS/400, that sells the AS/400. But only Rochester would know that. rd
Comment