Pandemonium Medicine Show

JXTA Configuration Podcast Slides

I've done most of my work using the 2.0 Solaris version but the new 2.1 version is expected soon. In addition to a new thread visualization tool, new DTrace scripts and other improvements the big news for the 2.1 release is that Java RTS now supports Linux. Two realtime Linux distributions have been qualified so far and more can probably be expected.

The presentation isn't about the mechanics (the how) of JXTA configuration but is instead focused entirely at the why of JXTA configuration. I've also been trying to make the presentation as self contained as possible, a reader or (eventually) a listener shouldn't need to have any prior understanding of JXTA's inner workings in order to make sense of what is discussed. I've been somewhat unsure about what level of experience with networking should be assumed though. Should I assume that readers know what a firewall is? Should I assume that they know that SMTP is used for sending email messages? Should I assume that readers know the RFC numbers and port assignments for the 100 most common network protocols? (Just kidding).

A week ago I asked a few people for feedback on the presentation to make sure I was going the right direction. The responses I got were very encouraging. In the last week I've prepared eight additional slides and I'm still enthusiastic that when completed this podcast will help many starting JXTA configurators. I've decided to start posting my drafts of the work in progress. I'll try to post an updated draft every week or so until the podcast is released. My primary goal in posting drafts is to make sure that the material remains on the right track. I'm interested in hearing feedback. I'm not too concerned, right now, with minor "There's a typo on slide 9, netowrk" type of errors. I'd rather hear about "You never explain what a peer is", kind of errors. (By the way, I guess I need to make a "What is a peer" slide....)

The current slide presentation with notes : JXTA Configuration

"Hey Guys, I've got a great idea. How about we use a non-standard connector for the USB interface on our new gadget?"

"Sounds great but the cable can only be 6 inches long and you can't charge the device via USB. We'll require using a charger that's unlike even the chargers we use for our other products."

"It'll be a non-international charger correct? And getting a replacement charger or one that uses another input voltage will be really expensive or nearly impossible."

"I can see it now. So there won't be a car charger, right. We won't make one and using a third party car charger will void the warranty!"

"Good, good, but even though the charger is different than our other chargers it will use the same charger tip as some of our other products."

"Will using the wrong charger permanently damage the device?"

"Yes, of course, why wouldn't it? We will make sure to mention it in the manual, but only in the troubleshooting section."

"Ok, that's enough for now. I hear that the PC software isn't crashing enough yet and can still be uninstalled without corrupting the operating system so we will discuss it next time. Meeting adjourned."

When Windows Media Centre Edition started imposing similar restrictions on HBO content in the middle of 2007 I cancelled my 10-year HBO subscription. Cya losers! If I owned a TiVo I would be unaffected by this most recent HBO blockage since I'm no longer an HBO customer (I'll rent your programs on DVD for a few pennies rather than the $10 a month I spent for a decade). I have little doubt though that TiVo will be asked to enforce that this type of restriction be applied to other programming if it isn't already and I'm not going to buy a VCR that doesn't work.

I don't understand why it is that TiVo or Microsoft would agree to enforce HBO's anti-fair use "though shalt not press record" decrees against their own customers. To be very clear--I am not asking TiVo or Microsoft to assist me with violating copyright law. I don't want to break copyright. I am merely asking for them to not impede my fair use rights.