Because of heavy processing requirements, we are currently using some of your unused brain capacity for backup processing. Please ignore any hallucinations, voices or unusual dreams you may experience. Please avoid concentration-intensive tasks until further notice. Thank you.
|Enterprise Java Beans|
Back in the '70s when I started beating on computers, if you wanted to compile and run a program you would hand in to the computer center a card deck containing:
Your buddy Joe once gave them a blank red card instead of an end-of-job card and they never checked if it was punched, which was pretty funny until the end-of-month accounting run was charged to your department because the computer charged the next job to Joe's cost center.
[dead link ... moved to openejb.org]
I've had a co-worker berate me at length because I'm clearly misrepresenting what EJB is all about. All these things have to be specified because there are half a dozen transaction mechanisms and other things that need to be specified, you can't leave them out.
That really doesn't matter. You know there were really good reasons for all those cards on the old days too. You have multiple record types for files, even text files, and multiple kinds of file systems with slightly different APIs for each, and so on. What happened is that we don't have multiple kinds of file systems and we have three kinds of text files and a program that accepts any combination of CR and LF as an end of line can read them all... and there were good reasons for people preferring each of the different file types and file system interfaces and so on...
In five or ten or twenty years all those defaults won't matter, either there will be one winner or you'll use the same API for all the options, and people will write five line servers and clients for the things people use EJB for. Maybe there will be a wrapper around this that just sets "the standard options", or maybe it'll be replaced. It doesn't matter. It'll all go the way of opening a file by setting up a 36 word file control block and a 20 or 24 word IO control block depending on the filesystem.
Even though Enterprise COBOL exists, maybe, just maybe, that's a fluke. Maybe, just maybe, we won't be programming our neural implants in XML and Java one day.
|Lynx-enhanced by <peter at taronga.com> (Peter da Silva)|