Daily Bytes

The Future of WiFi

href="http://www.wired.com/wired/archive/11.05/unwired/futurewifi.html">
Beyond Wi-Fi: What can we expect from the WiFi future. I find
the Mesh Networks specially attractive.

One of the most highly anticipated technologies, mesh
networking turns nearly any wireless device into a router, creating
an ad hoc network. Members of a network no longer rely on a central
routing hub to distribute data - instead, the information hops from
one user’s gadget to another until it gets where it’s going. Each
connected cell phone, PDA, or laptop pitches in a little routing
power, forming a spontaneous, temporary wireless cooperative. The
advantages include cheaper service and wider coverage areas. Plus,
proponents claim mesh can send data at speeds above 6 Mbps - about
15 times faster than DSL. Using higher bandwidth protocols like
UWB, those speeds could reach 500 Mbps. But there are challenges:
How will data remain secure as it passes from device to device
before reaching its destination? How can participants be billed for
connectivity? And dynamic routing can be complex; these systems
slow to a crawl if traffic is poorly managed.

Alternate Stylesheet

I was toying around with alternate stylesheets so if you want to
see the results you can use the onclick="setActiveStyleSheet('Black Sunset'); return false;">Black
Sunset Style link on the left menu.
Warning: This new style hasn’t been tested at all
(It works on my browser). If your hair starts falling or something
don’t come complaining to me.
On a more serious note, I’m known to be a terrible color picker so
don’t expect too much!
By the way, I stole the href="http://www.meyerweb.com/ui/styleswitch.js">javascript style
changing code from Eric
Meyer and the top image from href="http://dangerousmeta.com/posts/03/20030402#as">Garret, so
thanks and I hope you don’t mind

Lomboz

src="http://www.andrerestivo.com/weblog/archives/lomboz.gif"
width="102" height="128" border="0" align="right" /> href="http://www.objectlearn.com/index.jsp">Lomboz: I recently
restarted developing J2EE applications. Being an href="http://www.eclipse.org/">Eclipse addict I started by
searching for any J2EE relevant Eclipse plugins. That was when I
found Lomboz.

Lomboz is a great addition for any J2EE developer. It has lots of
wizards that generate new Modules and EJBs, JSP editors with auto
complete, Debugging, …

The best thing about Lomboz is that it creates all the needed Ant
files and at first I thought these should be enough to allow what I
really wanted the plugin for: Remote Deployment.

My Idea is to have several developers working with Eclipse and
Lomboz, commiting files via CVS to a central server where the J2EE
server (in this case JBoss) is running. As Lomboz generates the Ant
files needed to deploy the modules it should be fairly easy to
provide automatic module deployment through a web page. But it
isn’t!

A few quirks about the generated Ants are making this task harder
that I expected:

• Lomboz expects the J2EE server and Eclipse to be on the same
  machine meaning the build file expects to find some needed jars on
  the eclipse directory.
• The Ant build files don’t compile the code at all. They expect
  that Eclipse has already compiled it.
• The Ant files package all the compiled classes into all jar
  files making the division by modules seem quite uninteresting.

This doesn’t mean that Lomboz sucks, in fact it has a lot of
potential, but I’m going to have to do some work to get it working
the way I want. As soon as I get my build.xml together I will post
it here.