Keeping an old habit since the old times of C/C++ development and Makefile, mostly under Unix, I usually set environment variables to specify some properties that should be available during compiling or testing.
Well, my last blog post was about the Rio plugin of Mistral, and ended with an open (and expected) problem related to performance - something that I thought I'd have addressed in the next post.
... but most of the replies to my previous post "Where are we going?" (also at TheServerSide follow-up) ended up talking about closures etc. It sounds like nowadays it's inavoidable to talk about code and syntax. Too bad.
I returned from JavaPolis with a bag of mixed feelings.
*** edited to add: please be aware that Jan 11 meeting has been cancelled ***
January 2007 is a special month at JUG Milano: we will have two guests in a week, and two very important guests: Dennis Reedy and Jonas Boner.
Well, I'm an old bear, but since today is the last day of the year I'll make an exception and play the game.
After the BoF at JavaPolis (where the demo failed for some stupid connection problem in spite of the fact that half an hour earlier my setup was perfectly ok) and another code reorganization, we can talk about the Rio plugin for Mistral, which enables
Unfortunately in these days I don't have much time for blogging. Work is going on and we're optimizing the code for the Sun Grid in order to take advantage of the shared file system and to avoid serializing all the images through the network.
Unfortunately in these days I'm pretty busy and I don't have the time for extensively blogging - but I'm happy to say that Mistral, the imaging engine designed for extreme scalability from the multi-core up to the Grid, has been run successfully for the first time on the Sun Grid.