i like alur's affinity badges. clean and crisp. nice work. hey ... i see a myjxta badge. sweet! just added alur to my "klan jxta" roll. don't be the last one on your block not to be a klan jxta'ite.

regarding "blogs.sun.com :: chat," folks can add a personalized jnlp file that will effectively create an im room for the respective blog entry. quite trivially in fact and way more interactive then blog commentary ad nauseum. oh, and myjxta supports voice and video as well.

let me know if there are any takers and i'll help cook one up.

MyJXTA :: use it - learn it - do it

Java == platform independence
XML == application independence
JXTA == network independence

Secure End-to-End Computing

in my ears: Bloc Party/Silent Alarm/Like Eating Glass

that's a pic of my compadre in arms jeff moore, aka polo, who just commited a cut of myjxta that supports half and full duplex video. for the later you'll need to install jmf. we're looking for help with testing and broader platform support, namely osx.

here's the test myjxta video link'age. drop by and flash your mug.

next up we're going after a refactor that allows one to bind multiple dialogs/channels to any one plugin with an example being voice/video/text group chat. oh, there's much more work in the queue as well. myjxta is a stellar fun app to work with. great folks. unlimitted potential. don't take my word for it. witness the huge smile on polo's face. join the party.

you are now free to move about the network!

MyJXTA :: use it - learn it - do it

Java == platform independence
XML == application independence
JXTA == network independence

Secure End-to-End Computing

in my ears: A Perfect Circle/eMOTIVe/Passive

configuring jxta is easy enough, what about specializations? this entry touches upon the optimizer interface and how one can inject specialized logic into the jxta configuration process.

The optimizer feature of ext:config allows one to register app specific configuration optimization logic via a simple and well defined interface that can also be manged via a Profile, ie declaratively. One can add or remove as many optimizers as relevant to the task at hand.

One such optimizer was the results of a discussion whereby it was suggested that it is more efficient to deregister RendezVous if one is going to use a Relay service. Taking that use case into consideration, here is the corresponding logic:

Implement an optimizer:

import net.jxta.ext.config.Configurator;
import net.jxta.ext.config.optimizers.BaseOptmizer;

public class EdgeOptimizer
   extends BaseOptimizer {
    public void optimize(Configurator configurator) {
       if (configurator.getRelays().size() > 0) {
           configurator.clearRendezVous();
       }
   }
}

Next up, register the newly created optimizer with the respective profile by adding the following information:

 ...
 <configuration>
   <optimizer class="net.jxta.ext.config.optimizers.EdgeOptimizer"/>
 </configuration>
</jxta>

Lastly, bind this profile to AbstractConfigurator and you have now taylored your JXTA configuration process.

When considering one's JXTA deployment requirements there are likely a few optimizations that will come in handy and by using the above process the task of specializing the configuration process is easily achieved and infinitely extensible.

The "configuration" support within the profile supports passing nested name-value parameters as well, as implemented with the default RelayOptimizer:

...
 <configuration>
   <optimizer class="net.jxta.ext.config.optimizers.RelayOptimizer">
     <property name="reflection.service.bootstrap">
       http://rdv.jxtahosts.net/cgi-bin/reflection.cgi?2
     </property>
     <property name="reflection.service.max_wait">7</property>
   </optimizer>
 </configuration>
</jxta>

MyJXTA :: use it - learn it - do it

Java == platform independence
XML == application independence
JXTA == network independence

Secure End-to-End Computing

in my ears: RadioHead/Kid A/Optimistic

rehashed the jxta download site today. yup, it was that kind of a day.

pretty much making it up as i go along. trying to borrow good ideas yet stay within various process constraints with the goal being to incrementally make it better. as such, i welcome feedback. there are warts. i'm thinking about moving the ancillary links, those being maven and webstart up a page. well, they aren't ancillary per se but more akin to life blood ... but i digress.

ponder ...

here's the link again, jxta nightlies, so do feel free to pass along ideas of what works and what doesn't w/ the goal of making it better.

MyJXTA :: use it - learn it - do it

Java == platform independence
XML == application independence
JXTA == network independence

Secure End-to-End Computing

in my ears: Depeche Mode/Remixes 81-04/Shout

i posted this internally the other day ... in hindsight i should've posted it here and then dispatched the associated email pointers.

regardless, here's the skinny. one can configure jxta in roughly 3 (core) lines of code ... and here's how:

import net.jxta.ext.config.AbstractConfigurator;
import net.jxta.ext.config.Configurator;
import net.jxta.exception.ConfiguratorException;
import net.jxta.impl.peergroup.PlatformConfigurator;

public class MyConfigurator
extends AbstractConfigurator {
 public PlatformConfig createPlatformConfig(PlatformConfigurator configurator)
 throws ConfiguratorException {
   ((Configurator)configurator).setName("foo");
   ((Configurator)configurator).setSecurity("bar", "bop");

   return configurator.getPlatformConfig();
 }
}

now, in order to register your newly minted implemenation as the platform configuration delegate a registration one liner is all that is needed to close the loop:

import net.jxta.ext.config.AbstractConfigurator;
...
AbstractConfigurator.register(MyConfigurator.class);
...

jxta configuration is trivial. check it out. you can do way more with ext:config then what is exemplified in this trivial code frag.

MyJXTA :: use it - learn it - do it

Java == platform independence
XML == application independence
JXTA == network independence

Secure End-to-End Computing

in my ears: Depeche Mode/Ibiza/I Feel Love

now you can see the myjxta2 crew hard at work:

MyJXTA :: use it - learn it - do it

Java == platform independence
XML == application independence
JXTA == network independence

Secure End-to-End Computing

in my ears: Orbital/Blue Album/You Lot

i just finished my first cut at updating the jxta hands-on-lab that will be provided free to java one attendees and for purchase aftwards at an extremely affordable subscription price.

the team that manages the hol integration is pretty amazing. they make the process feel painless, host the events and pull it all together in a way that is seemless to lab participants as they freely delve into a couple of labs of their liking. as such, the j1 hol is a great learning opportunity if you have yet to give it a spin.

MyJXTA :: use it - learn it - do it

Java == platform independence
XML == application independence
JXTA == network independence

Secure End-to-End Computing

in my ears: The Clash/Story Of The Class/Rock The Casbah

i'm not a fan of [ed update] sour beer sour beer any more then the next lad. for the record, i'm a fraziskaner fan. mmmmmmmm tasty. let's pay homage to the fraziskaner kin of the world for a brief moment.

anyways, in wanting to do my part in ridding the world of sour beer (likely a new fangled form of rfe me thinks), i have retooled the myjxta builds so that the source distribution is atomically buildable and structurally inline with the sister binary distribution. should have done this awhile back, primarily for those that wish not to build from cvs.

to see if the new brew is palitable, please consider:

• visit the jxta downloads
• copy and expand any of the myjxta build artificats locally , eg jxta-myjxta-src-YYYYMMDD.zip
• peruse the included readme.txt checking to see if the bar stools, i mean bases, are covered sufficiently

if the elixer is not to your liking please ping me and we'll work to sweeten the recipe for the next (nightly) batch. if the new mix is to your liking, cheers.

if this build proves helpful we should be able to replicate the pattern down the project stack to cover platform, shell, and cms.

once we rid terra firma of sour beer we can then tak on curdled milk. priorities.

MyJXTA :: use it - learn it - do it

Java == platform independence
XML == application independence
JXTA == network independence

Secure End-to-End Computing

in my ears: Cult/Beyond Good And Evil/True Believers

work'n new myjxta ui mods, mad props to the hie folks:

and there's that little voice option again. what the $%^@ is that all about anyways?

MyJXTA :: use it - learn it - do it

Java == platform independence
XML == application independence
JXTA == network independence

Secure End-to-End Computing

in my ears: Filter/Title Of Record/Miss Blue

hmmmmmmmm, what is this i spy w/ my little eye ...

voice over jxta. how $%#@!*& sweet is that! and the price of admission is free.

mad props to frosty for the much needed css luv me wee blog needed!

MyJXTA :: use it - learn it - do it

Java == platform independence
XML == application independence
JXTA == network independence

Secure End-to-End Computing

in my ears: Grand National/Kicking The National Habit/Drink To Moving On

a voice-over-myjxta forum has now sprung up following the recent article. it's all good!

MyJXTA :: use it - learn it - do it

Java == platform independence
XML == application independence
JXTA == network independence

Secure End-to-End Computing

in my ears: Snow Patrol/Final Straw/Somwhere A Clock Is Ticking

got some java lobby love today which is always a great way to start the day. here's the quote from the article in full:

MyJXTA2 Gets Audio

Over the weekend, James Todd of JXTA fame dropped me an IM letting me know that there was some more JXTA goodness coming up soon. Apparently, a contributor sent in some new code that allows MyJXTA2 to handle sending audio over the Java P2P library. I think its great that JXTA is making such progress and this new addition enables us to begin thinking about things similar to a Java clone of Skype (for whatever reason we would want to do that!) and it’s the start of online conferencing technology over Java P2P (now if they could just send video). This afternoon I received a demo of the VOIP and I was blown away! Now, this new functionality is cool, but I'm still not sure whether it has made it into the nightly builds yet. You'll need to stay tuned to the JXTA website or try out the nightly web start builds of MyJXTA2 until the new functionality comes up. Tomorrow, I hope to have a thread about it at JL with some slick screenshots. We also hope to have a slick article (or maybe a series of articles?) about JXTA which will hopefully de-mystify some of the difficulty that often surrounds starting a new project with this powerful technology.

can you hear me now? yes. yes i can.

MyJXTA :: use it - learn it - do it

Java == platform independence
XML == application independence
JXTA == network independence

Secure End-to-End Computing

in my ears: Snow Patrol/Final Straw/Wow

just posted some of the updates for the quarter to java.net. great to see the jxta c implemenation gain parity. for me personally getting the jxta maven reports churned out nighly has been a much needed process from which we should be able to repurpose much of the less complete build processes and in turn start running load and performance tests and the like. you don't know what you can't measure.

daniel has graciously offered to share his sd.west presenation time with us so that should be fun as we hope to cover some interesting ground.

MyJXTA :: use it - learn it - do it

Java == platform independence
XML == application independence
JXTA == network independence

Secure End-to-End Computing

in my ears: Portishead/Portishead/Elysium

got the jxta nightlies to include maven reports now. this is just the start as i hope to narrow down the existing ant workload by moving more the exceptional tasks, doc creation and the like, to maven.

i was able to support multiple source directories for the javac goal which is a great start but i have yet to find a generic means to accomplish this for all goals and reports ... short copying all the source into a common work directory. i'd love to hear words of wisdom from mavenites in this regard.

MyJXTA :: use it - learn it - do it

Java == platform independence
XML == application independence
JXTA == network independence

Secure End-to-End Computing

in my ears: Death Cab For Cutie/Transalanticism/The New Year

the quarterly bugday is upon us again. this build includes a runtime patch that addresses network configurations for those instances that may have been incomplete yet otherwise operational. this will soon be in the nightly build at which point all instances should be syncronized.

so, consider running the following and participate in the 2.3.3b bugday:

MyJXTA :: use it - learn it - do it

Java == platform independence
XML == application independence
JXTA == network independence

Secure End-to-End Computing

in my ears: Scorpions/Deadly Sting/Holiday