Skip to main content

Mike Duigou

Mike Duigou is an active developer on Project JXTA. he has been using his handle 'Bondolo' since he first joined the net community in 1984. Mike once founded an e-commerce software start-up with two friends long before it was fashionable. He now works for Sun Microsystems, Inc. and finds himself surprised, but thrilled, to be paid for working on open source software. Mike's first open source contributions were to the Citadel BBS software in 1987 and he has contributed other work regularly on a variety of projects. In addition to working on many parts of the JXTA J2SE implementation Mike is the editor of the JXTA Protocol Specification effort.

 

bondolo's blog

JXSE 2.5 : What's Cool #7 -- Logging

Posted by bondolo on October 14, 2007 at 12:37 PM PDT

JXSE (JXTA for Java SE/EE 5.0) 2.5 contains quite a number of exciting changes for JXTA application developers.

JXSE 2.5 : What's Cool #6 -- PeerGroup Executor and ScheduledExcutor

Posted by bondolo on October 9, 2007 at 10:32 AM PDT

JXSE (JXTA for Java SE/EE 5.0) 2.5 contains quite a number of exciting changes for JXTA application developers. This little series will look at a few of the important changes in the upcoming release.

JXSE 2.4 was the first version to require Java Standard Edition 5.0. For that release we used only a small amount of JSE 5 specific functionality.

JXSE 2.5 : What's Cool #5 -- java.util.concurrent

Posted by bondolo on September 20, 2007 at 2:03 PM PDT

JXSE (JXTA for Java SE/EE 5.0) 2.5 contains quite a number of exciting changes for JXTA application developers. This little series will look at a few of the important changes in the upcoming release.

JXSE 2.4 was the first version to require Java Standard Edition 5.0. For that release we used only a small amount of JSE 5 specific functionality.

JXSE 2.5 : What's Cool #4 -- Generics & enums

Posted by bondolo on September 13, 2007 at 2:54 PM PDT

JXSE (JXTA for Java SE/EE 5.0) 2.5 contains quite a number of exciting changes for JXTA application developers. This little series will look at a few of the important changes in the upcoming release.

JXSE 2.4 was the first version to require Java Standard Edition 5.0. For that release we used only a small amount of JSE 5 specific functionality.

JXSE 2.5 : What's Cool #2 -- META-INF/services

Posted by bondolo on September 12, 2007 at 2:33 PM PDT

JXSE (JXTA for Java SE/EE 5.0) 2.5 contains quite a number of exciting changes for JXTA application developers.

JXSE 2.5 : What's Cool #3 -- Programmers Guide 2.5

Posted by bondolo on September 12, 2007 at 2:32 PM PDT

JXSE (JXTA for Java SE/EE 5.0) 2.5 contains quite a number of exciting changes for JXTA application developers. This little series will look at a few of the important changes in the upcoming release.

One of the most exciting new developments related to JXSE 2.5 is the new edition of the JXSE Programmers Guide that will accompany it's release.

JXSE 2.5 : What's Cool #1 : NIO TCP

Posted by bondolo on September 5, 2007 at 2:46 PM PDT

JXSE (JXTA for Java SE/EE 5.0) 2.5 contains quite a number of exciting changes for JXTA application developers. This little series will look at a few of the important changes in the upcoming release.

JXSE provides two primary low-level message transports; TCP and HTTP.

The JXTA Migration

Posted by bondolo on June 29, 2007 at 9:01 AM PDT

For the last couple of weeks the JXTA project has gone through the difficult process of moving. Moving an open source project is, in most ways, easier than moving in the real world. For one thing, we haven't had to bribe our friends with beer and pizza in order to get them to help.

PSE Access Service

Posted by bondolo on April 14, 2006 at 11:09 AM PDT

A couple of weeks ago I mentioned a new PSE based Access Service for JXTA. Well, a primordial version has now appeared as part of issue #1517. The current version is functional, but not deployable since it isn't actually secure.

Big Changes to JXTA Configuration

Posted by bondolo on November 2, 2004 at 9:05 AM PST

There has been a lot of recent work on improving and simplifying the JXTA configuration process. A lot of the work has focused on the extension config package, but there are big changes in the "classic" JXTA Configuration Dialog too.

But isn't the "classic" AWT config dialog obsolete? Yep, it is in most ways. We're no longer trying to put ever configuration feature into it.