You are correct sir, I have just released MyPenis to the public domain under the GPL. MyPenis is now open source "feel" free to make extensive use of it!
New York -- In October, an intelligence alert went out to a small number of government agencies, including the Energy Department's top-secret Nuclear Emergency Search Team, based in Nevada. The report said that terrorists were thought to have obtained a 10-kiloton nuclear weapon from the Russian arsenal, and planned to smuggle it into New York City, a special TIME magazine investigation reveals.
JKatz yesterday admitted to Slashdot that he was behind the molestation of youth from the around the country. His reason? The children were naughty and didn't respect thier elders. Still, there has to be more to it than that for JKatz to molest them so quickly and unexpectedly, especially since he has a large userbase of gay 'lin-uks' users at his disposal.
...The criminals and the woefully stupid would pay for a terrible site like slashdot. We should round up the slashbot subscribers and put them into rehabilitation camps, then take all the Janitor and put them back to work at fast-food jobs where they belong.
Oprah said that 80 - 90% of ALL online traffic is pornographic in nature, and Oprah is NEVER wrong.
From this perfect statistic we can deduce that...
If you want a new internet technology to survive you must get the porn industry to support it!
REPOST: FOR THOSE OF YOU WHO MISSED THE FIRST ONE
on
Java RMI
·
· Score: 0, Insightful
The Scoop
Remote Method Invocation (RMI) is the object-oriented remote procedure call (ORPC) facility for distributed programming in Java, since the 1.1 days. RMI also served as motivation and a proof-of-concept for jini, javaspaces , and numerous other solid distributed networking technologies. Of course, anyone from the academic distributed programming world knows Wollrath, Waldo, and Riggs.
Yet, despite a myriad of books over the past five years on network programming, RMI always seemed to be the stepchild: relegated to a single chapter (buried on page 496, of course) that always said that RMI was "better" than sockets and "worse" than CORBA. Now, granted that RMI is operationally rather trivial compared with CORBA and was (prior to RMI/IIOP ) a unilanguage distributed ORPC technology -- but still. For those of us who have to interoperate with RMI (whether welcome from the Java world or not), the lack of in-depth technical analysis (beyond the spec) has been a hindrance.
Fortunately, this trend is finally starting to buckle with the release of several in-depth RMI books including: Java RMI, Java.rmi, and Mastering RMI: Developing Enterprise Applications in Java and EJB . As evidence of this problem, Grosso states the same in his introduction ? and actually pulls it off without sounding self-serving.
I chose Grosso's text because of the cute squirrel (aka the O'Reilly brand), Grosso's recent series of articles on the hashbelt algorithm, and his unadulterated academic knowledge management and mathematics bent. Fortunately, I was rewarded: this animal returns to O'Reilly's pre-bubble quality. Koodoos to both Grosso and his editors (Knudsen, Loukides, and Eckstein) for getting the train back on the track.
What's to Like
Bottom line is that Grosso simply covers the topics and does so with solid conceptual and code coherence ? even by O'Reilly standards (over 40 animals grace my shelves). His prose and explanatory patterns make it clear that he has actually gotten into the real-world of RMI, and doesn't hesitate to highlight both good and bad parts. You cannot be dozing off when you read this (at least not if you expect to understand it) -- this is written by someone with solid analytic thinking skills and it shows. After too many years of "there are no caveats" journalism and publishing, this is a nice reversion. Further, I can only imagine that his current employment is a testament to his real-world knowledge of RMI.
Grosso hits on a vein which is not well-appreciated: when not smoothed over by marketing people, RMI is actually a mostly-capable ORPC technology. Certainly activation and RMI/IIOP really began to make things interesting, from Java2 and EJB respectively. Discussion of reference-counted distributed garbage collection, a feature missing from CORBA and other popular ORPC standards, also contributes a nice bonus (although Grosso's ardent attempt to debunk the "RMI doesn't scale" argument is rather weak, even going so far as to rehash the definition of Threads and threadpools ? this complexity mismatch is an ugly giveaway that a well-intentioned editor went astray).
What sets this text apart is the tight focus on nitty-gritty implementation details of RMI itself. After all, these RMI texts are way too late to the game to reteach how to write "baby RMI" code: 5 years after the original spec, you either know how to write RMI or you don't. Grosso simply gives you a solid in-depth analysis of all the obscurities of the RMI runtime, custom sockets, dynamic classloading, activation, MarshalledObjects, and HTTP tunneling. In other words, all the interesting real-world topics whose official documentation is poor and which the various RMI tutorials (written many years ago) ignored.
While canonical, the single banking example followed through the text was well-executed, although authors continue to underestimate the prevalence of readers who consume textbooks non-linearly.
What's Not to Like
RMI/IIOP is shaping up to be a fascinating contributor to the "cleanup the EJB mess" discussion. Dedicating a measly 13 pages (beginning on page 503, no less) to this critical topic seems a bit of an oversight ? but maybe that is just my CORBA sentiments speaking. Either way, the mechanics of CORBA are sufficiently intricate in real-world deployments that saying "if you can build an RMI system, you can build a CORBA system" (p. 511) is a bit brazen (or naïve) for my tastebuds. I can only chalk up this oversight to deadline pressure, which is probably a Good Thing?, since the book was supposedly in production over almost 2 years.
A minor point: the top-level organization of the book (Part I, II, III) is arbitrary, ignore it -- use the chapter organization instead.
The Summary
Quality: solid practical insight into the nitty-gritty operational implementation details of RMI in the real-world. You simply are not going to find solid O'Reilly-quality coverage of the topics elsewhere.
Relevance: If you are responsible for making RMI actually work in production systems, this might well be the next animal on your shelf ? either now or later. If you want a breezy afternoon saunter around RMI, skip this. Instead, google one (of the many) free tutorials online."
Slashdot Mirror
I just found a major flaw in the "spell-casting" software, I will post more details as I pull them out of John Katz'es Ass.
All the Dirty Linux Hippies get togather and work on ONE distro instead of having little tribes of stinky worthless POS Linux Distros.
With a superior OS like XP being offered by Microsoft how can linux even hope to compete?
The fact is: Linux is Doomed!
You are correct sir, I have just released MyPenis to the public domain under the GPL. MyPenis is now open source "feel" free to make extensive use of it!
You just described XP, It's the BEST OS ever!
Who needs memory management, IO, SMP or any of that other technical mumbo-jumbo.
We come in peace, Microsoft is your friend!
Line installed in my ass, the reception isn't coming in too well...
Then I got caught masturbating to pictures of richard simmons.
It looks like a giant swollen pimple!
QUICK SOMEONE POP IT!!!!!!!!!!!
Slashbot Janitors, YOU SUCK!
Thank you
New York -- In October, an intelligence alert went out to a small number of government agencies, including the
Energy Department's top-secret Nuclear Emergency Search Team, based in Nevada. The report said that terrorists
were thought to have obtained a 10-kiloton nuclear weapon from the Russian arsenal, and planned to smuggle it
into New York City, a special TIME magazine investigation reveals.
I hope they do it right this time...
Thats how John Katz likes them, young and ripe.
And A fine FUck you to the Janitors, your hard work is laughed at, fuck off and die!
JKatz yesterday admitted to Slashdot that he was behind the molestation of youth from the around the country. His reason? The children were naughty and didn't respect thier elders. Still, there has to be more to it than that for JKatz to molest them so quickly and unexpectedly, especially since he has a large userbase of gay 'lin-uks' users at his disposal.
...The criminals and the woefully stupid would pay for a terrible site like slashdot. We should round up the slashbot subscribers and put them into rehabilitation camps, then take all the Janitor and put them back to work at fast-food jobs where they belong.
First Post!
RWD 2002
I have decided to open source my penis, it is now available under the terms of the GPL.
Praise Free Software!
It's an MS mole sent to infect ./ with sloppy MS brainwashing techneeq!
Down With Mundie, I love Linux, Viva the GPL!
Dissention is Terrorism, Silence Women!
Will you Marry Me?
Dude, John Katz called. He wants his massive black dildo back.
Oprah said that 80 - 90% of ALL online traffic is pornographic in nature, and Oprah is NEVER wrong.
From this perfect statistic we can deduce that...
If you want a new internet technology to survive you must get the porn industry to support it!
The Scoop
Remote Method Invocation (RMI) is the object-oriented remote procedure call (ORPC) facility for distributed programming in Java, since the 1.1 days. RMI also served as motivation and a proof-of-concept for jini, javaspaces , and numerous other solid distributed networking technologies. Of course, anyone from the academic distributed programming world knows Wollrath, Waldo, and Riggs.
Yet, despite a myriad of books over the past five years on network programming, RMI always seemed to be the stepchild: relegated to a single chapter (buried on page 496, of course) that always said that RMI was "better" than sockets and "worse" than CORBA. Now, granted that RMI is operationally rather trivial compared with CORBA and was (prior to RMI/IIOP ) a unilanguage distributed ORPC technology -- but still. For those of us who have to interoperate with RMI (whether welcome from the Java world or not), the lack of in-depth technical analysis (beyond the spec) has been a hindrance.
Fortunately, this trend is finally starting to buckle with the release of several in-depth RMI books including: Java RMI, Java.rmi, and Mastering RMI: Developing Enterprise Applications in Java and EJB . As evidence of this problem, Grosso states the same in his introduction ? and actually pulls it off without sounding self-serving.
I chose Grosso's text because of the cute squirrel (aka the O'Reilly brand), Grosso's recent series of articles on the hashbelt algorithm, and his unadulterated academic knowledge management and mathematics bent. Fortunately, I was rewarded: this animal returns to O'Reilly's pre-bubble quality. Koodoos to both Grosso and his editors (Knudsen, Loukides, and Eckstein) for getting the train back on the track.
What's to Like
Bottom line is that Grosso simply covers the topics and does so with solid conceptual and code coherence ? even by O'Reilly standards (over 40 animals grace my shelves). His prose and explanatory patterns make it clear that he has actually gotten into the real-world of RMI, and doesn't hesitate to highlight both good and bad parts. You cannot be dozing off when you read this (at least not if you expect to understand it) -- this is written by someone with solid analytic thinking skills and it shows. After too many years of "there are no caveats" journalism and publishing, this is a nice reversion. Further, I can only imagine that his current employment is a testament to his real-world knowledge of RMI.
Grosso hits on a vein which is not well-appreciated: when not smoothed over by marketing people, RMI is actually a mostly-capable ORPC technology. Certainly activation and RMI/IIOP really began to make things interesting, from Java2 and EJB respectively. Discussion of reference-counted distributed garbage collection, a feature missing from CORBA and other popular ORPC standards, also contributes a nice bonus (although Grosso's ardent attempt to debunk the "RMI doesn't scale" argument is rather weak, even going so far as to rehash the definition of Threads and threadpools ? this complexity mismatch is an ugly giveaway that a well-intentioned editor went astray).
What sets this text apart is the tight focus on nitty-gritty implementation details of RMI itself. After all, these RMI texts are way too late to the game to reteach how to write "baby RMI" code: 5 years after the original spec, you either know how to write RMI or you don't. Grosso simply gives you a solid in-depth analysis of all the obscurities of the RMI runtime, custom sockets, dynamic classloading, activation, MarshalledObjects, and HTTP tunneling. In other words, all the interesting real-world topics whose official documentation is poor and which the various RMI tutorials (written many years ago) ignored.
While canonical, the single banking example followed through the text was well-executed, although authors continue to underestimate the prevalence of readers who consume textbooks non-linearly.
What's Not to Like
RMI/IIOP is shaping up to be a fascinating contributor to the "cleanup the EJB mess" discussion. Dedicating a measly 13 pages (beginning on page 503, no less) to this critical topic seems a bit of an oversight ? but maybe that is just my CORBA sentiments speaking. Either way, the mechanics of CORBA are sufficiently intricate in real-world deployments that saying "if you can build an RMI system, you can build a CORBA system" (p. 511) is a bit brazen (or naïve) for my tastebuds. I can only chalk up this oversight to deadline pressure, which is probably a Good Thing?, since the book was supposedly in production over almost 2 years.
A minor point: the top-level organization of the book (Part I, II, III) is arbitrary, ignore it -- use the chapter organization instead.
The Summary
Quality: solid practical insight into the nitty-gritty operational implementation details of RMI in the real-world. You simply are not going to find solid O'Reilly-quality coverage of the topics elsewhere.
Relevance: If you are responsible for making RMI actually work in production systems, this might well be the next animal on your shelf ? either now or later. If you want a breezy afternoon saunter around RMI, skip this. Instead, google one (of the many) free tutorials online."
Fr0st P1st!
Katz anus on a friday night at the janitor office!
ARE a dirty GNU/Linux ass humping hippy who is a blight upon the open sores community. I hope you are molested by a gaggle of rock wielding retards.
RWD 2002
With all the extra cash generated from the ads you need to fire the GAYEST SLASH-JANITOR of them all Jon Katz, and hire someone with REAL talent.
RWD 2002, Retards Don't Read Ads