embedlets-developer

[Embedlets-dev] Global Light Blinker Project proposal

[Ted K. <tk...@ya...>]

Embedlets Group,

It has been 9 month since we started the Embedlets project and in my opinion it
is time to start letting the world know about our existence.  I originally
thought that the Enterprise Outpost would be the way that Embedlets would first
be introduced to the world but that plan's dependency on a graphic wiring tool
has slowed it down just a bit.

But the Embedlet Container works now! Even though we still need to work through
a number of issues before Embedlets is ready for commercial use, like JAPL, I
think we have a solid enough of an implementation to start pursuing
noncommercial quality beta projects.

And I think I accidentally stumbled upon a killer 'coming out' project for
Embedlets!

I call it the Global Light Blinker project and the idea was conceived on the
newcim list that I am a member of:

http://groups.yahoo.com/group/newcim/

These guys want to build an experimental globally distributed CNC light blinker
system and so I have been researching how to do this for the past 2 weeks.  At
JavaOne, Bruce Boyes had convinced me to seriously start looking into JXTA and,
as it turns out, a JXTA/Embedlet container combination appears to be a killer
technology!

Here is a diagram of the light blinker hardware that will be needed for this
project:

http://tkosan.javadevices.org/misc/embeddedjava/light_blinker_diagram.jpg


Here is where things get very interesting.  I have spent a large amount of time
during the past couple of weeks looking through the jxta.org site and reading
the jxta documentation and guess what?  None of the current or proposed JXTA
projects have any computer interfacing component to them at all.  The JXTA
group talks a lot about using JXTA to monitor sensors and control actuators but
evidently almost none of them have the expertise needed to deal with embedded
hardware.  But they seem to really want to...

IMHO, this would be a wonderful opportunity for the Embedlets Group to propose
a partnership with the JXTA group.  We would provide them with the Embedded
Systems expertise that they need and they would provide us with the
peer-to-peer expertise and project ideas that have Embedded Systems components
that we need.

This is something we can start pursuing now without needing the Embedlet
Container to be 100% commercially ready yet.


Here is a proposal for how to proceed with this:

1) Hammer out a feasible hardware design that is similar to the light blinker
diagram given above.

2) Find a company that is willing to build and sell the physical Light Blinker
kits (Serial-to-1-Wire converter and Light Blinker box).

3) Develop a Global Light Blinker joint JXTA/Embedlets project proposal that we
can submit to the JXTA group. (I will volunteer to do this).


What do people think?


In the mean time, the newcim group is very excited about blinking lights across
the globe and I am in the process of writing a distributed JXTA/Embedlets
application and assembling some test hardware to do this.

Ted

__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com

RE: [Embedlets-dev] Global Light Blinker Project proposal

[James C. <ca...@vi...>]

Hi Ted,

As always lots of good ideas's here. I suppose I should dust up my jxta
skills soon also. This project does get me wondering though.. Wondering
about what happened to outpost. I don't think the graphic wiring tool
was the thing that slowed it down. 

I wonder if we are going to make the effort to build something like this
that it shouldn't be more along the lines of an outpost demo that might
have a commercial impact rather than a hobbyst project.

The other thing we need to be careful of is not to dilute our efforts to
such an extent that progress stalls.

James Caska
www.muvium.com
uVM - 'Java Bred for Embedded'



-----Original Message-----
From: emb...@li...
[mailto:emb...@li...] On Behalf Of
Ted Kosan
Sent: Tuesday, 1 July 2003 8:11 AM
To: emb...@li...
Subject: [Embedlets-dev] Global Light Blinker Project proposal


Topic tags:[ARCH][JAPL][WIRING][DOCS][MGMT][STRATEGY][NEWBIE]
_______________________________________________

Embedlets Group,

It has been 9 month since we started the Embedlets project and in my
opinion it is time to start letting the world know about our existence.
I originally thought that the Enterprise Outpost would be the way that
Embedlets would first be introduced to the world but that plan's
dependency on a graphic wiring tool has slowed it down just a bit.

But the Embedlet Container works now! Even though we still need to work
through a number of issues before Embedlets is ready for commercial use,
like JAPL, I think we have a solid enough of an implementation to start
pursuing noncommercial quality beta projects.

And I think I accidentally stumbled upon a killer 'coming out' project
for Embedlets!

I call it the Global Light Blinker project and the idea was conceived on
the newcim list that I am a member of:

http://groups.yahoo.com/group/newcim/

These guys want to build an experimental globally distributed CNC light
blinker system and so I have been researching how to do this for the
past 2 weeks.  At JavaOne, Bruce Boyes had convinced me to seriously
start looking into JXTA and, as it turns out, a JXTA/Embedlet container
combination appears to be a killer technology!

Here is a diagram of the light blinker hardware that will be needed for
this
project:

http://tkosan.javadevices.org/misc/embeddedjava/light_blinker_diagram.jp
g


Here is where things get very interesting.  I have spent a large amount
of time during the past couple of weeks looking through the jxta.org
site and reading the jxta documentation and guess what?  None of the
current or proposed JXTA projects have any computer interfacing
component to them at all.  The JXTA group talks a lot about using JXTA
to monitor sensors and control actuators but evidently almost none of
them have the expertise needed to deal with embedded hardware.  But they
seem to really want to...

IMHO, this would be a wonderful opportunity for the Embedlets Group to
propose a partnership with the JXTA group.  We would provide them with
the Embedded Systems expertise that they need and they would provide us
with the peer-to-peer expertise and project ideas that have Embedded
Systems components that we need.

This is something we can start pursuing now without needing the Embedlet
Container to be 100% commercially ready yet.


Here is a proposal for how to proceed with this:

1) Hammer out a feasible hardware design that is similar to the light
blinker diagram given above.

2) Find a company that is willing to build and sell the physical Light
Blinker kits (Serial-to-1-Wire converter and Light Blinker box).

3) Develop a Global Light Blinker joint JXTA/Embedlets project proposal
that we can submit to the JXTA group. (I will volunteer to do this).


What do people think?


In the mean time, the newcim group is very excited about blinking lights
across the globe and I am in the process of writing a distributed
JXTA/Embedlets application and assembling some test hardware to do this.

Ted

__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com


-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01
_______________________________________________
Embedlets-developer mailing list
Emb...@li...
https://lists.sourceforge.net/lists/listinfo/embedlets-developer

RE: [Embedlets-dev] Global Light Blinker Project proposal

[Ted K. <tk...@ya...>]

James wrote:

> This project does get me wondering though.. Wondering
> about what happened to outpost. I don't think the graphic wiring tool
> was the thing that slowed it down. 

I think that Outpost is alive and well but the problem is that my version of a
Outpost marketing strategy has the following dependencies:

1) Graphic Wiring tool.
2) Deployment/Configuration mechanism.
3) Solid JAPL specification and implementations.
4) Standard way to connect an Outpost to a backend enterprise system.

We don't have any of these pieces yet and it looks like it is going to take us
a while to build them.  Beyond this we do not have any users using the code we
already do have which makes it difficult to move forward.



> I wonder if we are going to make the effort to build something like this
> that it shouldn't be more along the lines of an outpost demo that might
> have a commercial impact rather than a hobbyst project.

In the process of building something commercial, what happens if a great
sub-commercial opportunity is discovered that directly helps build towards
commercial-quality code?  

The funny thing about Java is that it is a very inaccurate (albeit powerful)
'weapon'.  Sun initially aimed Java at the Embedded Market and it endedded up
hitting the Enterprise market.  Here we initially aimed Java at the Enterprise
Market (with Enterprise Outpost) and I think there is a very good chance that
we are going to end up hitting the Home Embedded market.

If we go back to the main reason that the Outpost idea was conceived in the
first place, it was to find a large market for Embedded Java.  This overall
goal supersedes all lesser goals.  The Embedlets/Outpost project was designed
to be a vehicle to use to help with this discovery.

From my perspective the project is meeting its purpose excellently because I
know that I have a much better understanding of Embedded Java dynamics than I
did when we started this journey back in October.  I now think that I have a
fairly good grasp of what a good Embedded Java opportunity looks like and what
the Embedded Java pitfalls look like.


We have all put a heck of a lot of work into Embedlets/Embedded Java over the
past year and now I think it is time for some of that effort to pay off.  

In my opinion, the Global Light Blinker (GLB) project opens the door to the
greatest Embedded Java opportunity to come along since the concept of Embedded
Java was first developed and the Embedded Java community is currently the only
group on the planet which is in a position to pursue it.


Here are my reasons for thinking this:

1) The GLB project shows a large number of people what Embedded Java is capable
of without having to explain anything to them (the project's visibility
potential is enormous!).  As soon as they see their lamps turning on and off
remotely through the internet they will instantly 'get it'.

2) As soon as people's 'lights go on', how long do you think it is going to
take for them to come up with dozens of ideas for things to control inside of
the their homes that they can actually use?  How many of these people are
business people that will instantly see how they can sell devices like this to
other people?

3) At this moment in time, the main opportunity for building these devices, and
showing others how to build them, is being offered to the Embedded Java
Community (as defined by http://embedlets.org/images/flounder.jpg). The
Embedded Java developers represent the primary Community in the world that has
the correct mix of Hardware/Software skills needed to build these devices.

4) The great thing for us is that the 'remote control of in-home devices'
opportunity is in its very early stages because NAT has been an effective
roadblock which has prevented it from materializing.  JXTA 2.0 smashed this
roadblock a few months ago and now, very suddenly, the Embedded Java Community
has *secure* access into the home.  To get started, we don't need
commercial-quality hardware or a finished and commercial-quality Embedlets
implementation.  As incomplete as it is, the Embedlets implementation that we
currently have is more than ready for starting to pursue this opportunity.


To summarize, the Enterprise Outpost idea is a great idea, and we are slowly
getting there. In the process of building the Enterprise Outpost the Home
Device Outpost was discovered, and it has a large market that we can pursue
right now.



> The other thing we need to be careful of is not to dilute our efforts to
> such an extent that progress stalls.

I would say that progress on Embedlets is about to make a great leap forward. 
When viewed from the right perspective, a number of seemingly disconnected
efforts can be seen to actually be part of a well-coordinated effort.  Some
people's style when building a system is to work sequentially and to completely
finish the current component before moving on to the next step.  

A style that contrasts this is to work on all of the components in parallel so
that the quality of the interfaces between the components can be maximized and
also so that the system can be better tuned to fit its overall purpose.

I am definitely a parallel-development-style person so perhaps this knowledge
might ease your concerns a bit.



Anyway, for the past couple of weeks I have been working 'like a dog' to get my
mind around JXTA 2.0 with the goal of remotely blinking a house lamp which is
sitting behind NAT in someone's home.  I am so close now that I can 'almost
taste it' and with any luck the first LightBlinker should go live sometime this
weekend.

I have also already found a company that is willing to make the beta hardware
and I even convinced them to hire our University students to do the assembly. 
The hardware specification is going to be open so that anyone can implement
them but it is my guess that most people would rather just buy a reasonably
priced pre-assembled box.


But actually, the LightBlinker project is just a proof of concept, the real
opportunity is in meeting the demand for all of the other things that people
want to monitor and control in their homes.


So, is anyone here interested in this idea enough to discuss it further?


Ted

__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com

RE: [Embedlets-dev] Global Light Blinker Project proposal

[Kelly S. <be...@ea...>]

But Ted... Re: "Beyond this we do not have any users using the code we
already do have which makes it difficult to move forward."

I have not seen any "published" code.  Where is it?

Best regards, Kelly Smith (1-Wire/Java/TINI class advocate... your class
that is!) Smith

-----Original Message-----
From: emb...@li...
[mailto:emb...@li...]On Behalf Of Ted
Kosan
Sent: Friday, July 04, 2003 1:19 PM
To: emb...@li...
Subject: RE: [Embedlets-dev] Global Light Blinker Project proposal


Topic tags:[ARCH][JAPL][WIRING][DOCS][MGMT][STRATEGY][NEWBIE]
_______________________________________________

James wrote:

> This project does get me wondering though.. Wondering
> about what happened to outpost. I don't think the graphic wiring tool
> was the thing that slowed it down.

I think that Outpost is alive and well but the problem is that my version of
a
Outpost marketing strategy has the following dependencies:

1) Graphic Wiring tool.
2) Deployment/Configuration mechanism.
3) Solid JAPL specification and implementations.
4) Standard way to connect an Outpost to a backend enterprise system.

We don't have any of these pieces yet and it looks like it is going to take
us
a while to build them.  Beyond this we do not have any users using the code
we
already do have which makes it difficult to move forward.



> I wonder if we are going to make the effort to build something like this
> that it shouldn't be more along the lines of an outpost demo that might
> have a commercial impact rather than a hobbyst project.

In the process of building something commercial, what happens if a great
sub-commercial opportunity is discovered that directly helps build towards
commercial-quality code?

The funny thing about Java is that it is a very inaccurate (albeit powerful)
'weapon'.  Sun initially aimed Java at the Embedded Market and it endedded
up
hitting the Enterprise market.  Here we initially aimed Java at the
Enterprise
Market (with Enterprise Outpost) and I think there is a very good chance
that
we are going to end up hitting the Home Embedded market.

If we go back to the main reason that the Outpost idea was conceived in the
first place, it was to find a large market for Embedded Java.  This overall
goal supersedes all lesser goals.  The Embedlets/Outpost project was
designed
to be a vehicle to use to help with this discovery.

From my perspective the project is meeting its purpose excellently because I
know that I have a much better understanding of Embedded Java dynamics than
I
did when we started this journey back in October.  I now think that I have a
fairly good grasp of what a good Embedded Java opportunity looks like and
what
the Embedded Java pitfalls look like.


We have all put a heck of a lot of work into Embedlets/Embedded Java over
the
past year and now I think it is time for some of that effort to pay off.

In my opinion, the Global Light Blinker (GLB) project opens the door to the
greatest Embedded Java opportunity to come along since the concept of
Embedded
Java was first developed and the Embedded Java community is currently the
only
group on the planet which is in a position to pursue it.


Here are my reasons for thinking this:

1) The GLB project shows a large number of people what Embedded Java is
capable
of without having to explain anything to them (the project's visibility
potential is enormous!).  As soon as they see their lamps turning on and off
remotely through the internet they will instantly 'get it'.

2) As soon as people's 'lights go on', how long do you think it is going to
take for them to come up with dozens of ideas for things to control inside
of
the their homes that they can actually use?  How many of these people are
business people that will instantly see how they can sell devices like this
to
other people?

3) At this moment in time, the main opportunity for building these devices,
and
showing others how to build them, is being offered to the Embedded Java
Community (as defined by http://embedlets.org/images/flounder.jpg). The
Embedded Java developers represent the primary Community in the world that
has
the correct mix of Hardware/Software skills needed to build these devices.

4) The great thing for us is that the 'remote control of in-home devices'
opportunity is in its very early stages because NAT has been an effective
roadblock which has prevented it from materializing.  JXTA 2.0 smashed this
roadblock a few months ago and now, very suddenly, the Embedded Java
Community
has *secure* access into the home.  To get started, we don't need
commercial-quality hardware or a finished and commercial-quality Embedlets
implementation.  As incomplete as it is, the Embedlets implementation that
we
currently have is more than ready for starting to pursue this opportunity.


To summarize, the Enterprise Outpost idea is a great idea, and we are slowly
getting there. In the process of building the Enterprise Outpost the Home
Device Outpost was discovered, and it has a large market that we can pursue
right now.



> The other thing we need to be careful of is not to dilute our efforts to
> such an extent that progress stalls.

I would say that progress on Embedlets is about to make a great leap
forward.
When viewed from the right perspective, a number of seemingly disconnected
efforts can be seen to actually be part of a well-coordinated effort.  Some
people's style when building a system is to work sequentially and to
completely
finish the current component before moving on to the next step.

A style that contrasts this is to work on all of the components in parallel
so
that the quality of the interfaces between the components can be maximized
and
also so that the system can be better tuned to fit its overall purpose.

I am definitely a parallel-development-style person so perhaps this
knowledge
might ease your concerns a bit.



Anyway, for the past couple of weeks I have been working 'like a dog' to get
my
mind around JXTA 2.0 with the goal of remotely blinking a house lamp which
is
sitting behind NAT in someone's home.  I am so close now that I can 'almost
taste it' and with any luck the first LightBlinker should go live sometime
this
weekend.

I have also already found a company that is willing to make the beta
hardware
and I even convinced them to hire our University students to do the
assembly.
The hardware specification is going to be open so that anyone can implement
them but it is my guess that most people would rather just buy a reasonably
priced pre-assembled box.


But actually, the LightBlinker project is just a proof of concept, the real
opportunity is in meeting the demand for all of the other things that people
want to monitor and control in their homes.


So, is anyone here interested in this idea enough to discuss it further?


Ted

__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com


-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01
_______________________________________________
Embedlets-developer mailing list
Emb...@li...
https://lists.sourceforge.net/lists/listinfo/embedlets-developer

RE: [Embedlets-dev] Global Light Blinker Project proposal

[Ted K. <tk...@ya...>]

Kelly wrote:

> But Ted... Re: "Beyond this we do not have any users using the code we
> already do have which makes it difficult to move forward."

Hello Kelly, nice to hear from you again!


> I have not seen any "published" code.  Where is it?

http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/embedlets/

The 'releases' directory contains a stable version of the platform and the
other CVS directories contain the work-in-progress code.  So far, all of the
experiemnts that I have done with the Outpost Embedlet container indicate that
it is very stable and usable now if we can just figure out a good approach for
attaching it to 'hardware things'.

If this were a standard pure-software project we would have had an official
release already but since Embedlets is a Hardware/Software hybrid project the
software is not useful to anyone without it being able to control hardware.

As I had indicated in an earlier post, there are still a number of hurdles to
overcome before Embedlets is ready for an official release (like JAPL and the
Configuration mechanism, etc.) but the core Embedlet container code base
appears to be very solid.  More than solid enough to pursue the Global Light
Blinker and similar projects.


So, what do you think about the Global Light Blinker idea?


Ted

__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com

RE: [Embedlets-dev] Global Light Blinker Project proposal

[James C. <ca...@vi...>]

Well Ted,

Why didn't you SAY SO!!

Well done.. It's a very good point that you don't always hit the target
you are aiming for.. I am impressed that you have got so far as to have
a manufacturer and working model which is driving your confidence.

I must admit I am not paying as much attention as I should be. So this
idea is to allow Home automation meaning people can connect to their
homes webbrowser and turn lights on and off?

BTW - for the dummies.. What is NAT?

James Caska
www.muvium.com
uVM - 'Java Bred for Embedded'



-----Original Message-----
From: emb...@li...
[mailto:emb...@li...] On Behalf Of
Ted Kosan
Sent: Friday, 4 July 2003 10:19 PM
To: emb...@li...
Subject: RE: [Embedlets-dev] Global Light Blinker Project proposal


Topic tags:[ARCH][JAPL][WIRING][DOCS][MGMT][STRATEGY][NEWBIE]
_______________________________________________

James wrote:

> This project does get me wondering though.. Wondering
> about what happened to outpost. I don't think the graphic wiring tool 
> was the thing that slowed it down.

I think that Outpost is alive and well but the problem is that my
version of a Outpost marketing strategy has the following dependencies:

1) Graphic Wiring tool.
2) Deployment/Configuration mechanism.
3) Solid JAPL specification and implementations.
4) Standard way to connect an Outpost to a backend enterprise system.

We don't have any of these pieces yet and it looks like it is going to
take us a while to build them.  Beyond this we do not have any users
using the code we already do have which makes it difficult to move
forward.



> I wonder if we are going to make the effort to build something like 
> this that it shouldn't be more along the lines of an outpost demo that

> might have a commercial impact rather than a hobbyst project.

In the process of building something commercial, what happens if a great
sub-commercial opportunity is discovered that directly helps build
towards commercial-quality code?  

The funny thing about Java is that it is a very inaccurate (albeit
powerful) 'weapon'.  Sun initially aimed Java at the Embedded Market and
it endedded up hitting the Enterprise market.  Here we initially aimed
Java at the Enterprise Market (with Enterprise Outpost) and I think
there is a very good chance that we are going to end up hitting the Home
Embedded market.

If we go back to the main reason that the Outpost idea was conceived in
the first place, it was to find a large market for Embedded Java.  This
overall goal supersedes all lesser goals.  The Embedlets/Outpost project
was designed to be a vehicle to use to help with this discovery.

From my perspective the project is meeting its purpose excellently
because I know that I have a much better understanding of Embedded Java
dynamics than I did when we started this journey back in October.  I now
think that I have a fairly good grasp of what a good Embedded Java
opportunity looks like and what the Embedded Java pitfalls look like.


We have all put a heck of a lot of work into Embedlets/Embedded Java
over the past year and now I think it is time for some of that effort to
pay off.  

In my opinion, the Global Light Blinker (GLB) project opens the door to
the greatest Embedded Java opportunity to come along since the concept
of Embedded Java was first developed and the Embedded Java community is
currently the only group on the planet which is in a position to pursue
it.


Here are my reasons for thinking this:

1) The GLB project shows a large number of people what Embedded Java is
capable of without having to explain anything to them (the project's
visibility potential is enormous!).  As soon as they see their lamps
turning on and off remotely through the internet they will instantly
'get it'.

2) As soon as people's 'lights go on', how long do you think it is going
to take for them to come up with dozens of ideas for things to control
inside of the their homes that they can actually use?  How many of these
people are business people that will instantly see how they can sell
devices like this to other people?

3) At this moment in time, the main opportunity for building these
devices, and showing others how to build them, is being offered to the
Embedded Java Community (as defined by
http://embedlets.org/images/flounder.jpg). The Embedded Java developers
represent the primary Community in the world that has the correct mix of
Hardware/Software skills needed to build these devices.

4) The great thing for us is that the 'remote control of in-home
devices' opportunity is in its very early stages because NAT has been an
effective roadblock which has prevented it from materializing.  JXTA 2.0
smashed this roadblock a few months ago and now, very suddenly, the
Embedded Java Community has *secure* access into the home.  To get
started, we don't need commercial-quality hardware or a finished and
commercial-quality Embedlets implementation.  As incomplete as it is,
the Embedlets implementation that we currently have is more than ready
for starting to pursue this opportunity.


To summarize, the Enterprise Outpost idea is a great idea, and we are
slowly getting there. In the process of building the Enterprise Outpost
the Home Device Outpost was discovered, and it has a large market that
we can pursue right now.



> The other thing we need to be careful of is not to dilute our efforts 
> to such an extent that progress stalls.

I would say that progress on Embedlets is about to make a great leap
forward. 
When viewed from the right perspective, a number of seemingly
disconnected efforts can be seen to actually be part of a
well-coordinated effort.  Some people's style when building a system is
to work sequentially and to completely finish the current component
before moving on to the next step.  

A style that contrasts this is to work on all of the components in
parallel so that the quality of the interfaces between the components
can be maximized and also so that the system can be better tuned to fit
its overall purpose.

I am definitely a parallel-development-style person so perhaps this
knowledge might ease your concerns a bit.



Anyway, for the past couple of weeks I have been working 'like a dog' to
get my mind around JXTA 2.0 with the goal of remotely blinking a house
lamp which is sitting behind NAT in someone's home.  I am so close now
that I can 'almost taste it' and with any luck the first LightBlinker
should go live sometime this weekend.

I have also already found a company that is willing to make the beta
hardware and I even convinced them to hire our University students to do
the assembly. 
The hardware specification is going to be open so that anyone can
implement them but it is my guess that most people would rather just buy
a reasonably priced pre-assembled box.


But actually, the LightBlinker project is just a proof of concept, the
real opportunity is in meeting the demand for all of the other things
that people want to monitor and control in their homes.


So, is anyone here interested in this idea enough to discuss it further?


Ted

__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com


-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01
_______________________________________________
Embedlets-developer mailing list
Emb...@li...
https://lists.sourceforge.net/lists/listinfo/embedlets-developer

RE: [Embedlets-dev] Global Light Blinker Project proposal

[Christopher S. <cs...@oo...>]

Ted,

I certainly am.

My experience in the lighting control business is actually quite extensive.
In the early 90's I designed a system to run the lighting for large
commercial buildings. Based on the Intel 8051 and the twisted wire BitBus
network we were able to control buildings with up to 250 networked panels
each controlling 255 light circuits. This was installed in the tallest
building in Los Angeles, the Library Square. (The one that they 'fried' in
the movie Indepdenance Day) and many others around the country.

My point to this is that there is also a large market to efficiently manage
the energy consumption in commercial buildings, especially with a system
that would not require rewiring existing  buildings.

The issues are similar to those in the home (security, ease of installation,
remote management etc.) but also involve tieing in to the tenant management
and billing systems as well.

Fun stuff!

Chris
>
> Topic tags:[ARCH][JAPL][WIRING][DOCS][MGMT][STRATEGY][NEWBIE]
> _______________________________________________
>
> Well Ted,
>
> Why didn't you SAY SO!!
>
> Well done.. It's a very good point that you don't always hit the target
> you are aiming for.. I am impressed that you have got so far as to have
> a manufacturer and working model which is driving your confidence.
>
> I must admit I am not paying as much attention as I should be. So this
> idea is to allow Home automation meaning people can connect to their
> homes webbrowser and turn lights on and off?
>
> BTW - for the dummies.. What is NAT?
>
> James Caska
> www.muvium.com
> uVM - 'Java Bred for Embedded'
>
>
>
> -----Original Message-----
> From: emb...@li...
> [mailto:emb...@li...] On Behalf Of
> Ted Kosan
> Sent: Friday, 4 July 2003 10:19 PM
> To: emb...@li...
> Subject: RE: [Embedlets-dev] Global Light Blinker Project proposal
>
>
> Topic tags:[ARCH][JAPL][WIRING][DOCS][MGMT][STRATEGY][NEWBIE]
> _______________________________________________
>
> James wrote:
>
> > This project does get me wondering though.. Wondering
> > about what happened to outpost. I don't think the graphic wiring tool
> > was the thing that slowed it down.
>
> I think that Outpost is alive and well but the problem is that my
> version of a Outpost marketing strategy has the following dependencies:
>
> 1) Graphic Wiring tool.
> 2) Deployment/Configuration mechanism.
> 3) Solid JAPL specification and implementations.
> 4) Standard way to connect an Outpost to a backend enterprise system.
>
> We don't have any of these pieces yet and it looks like it is going to
> take us a while to build them.  Beyond this we do not have any users
> using the code we already do have which makes it difficult to move
> forward.
>
>
>
> > I wonder if we are going to make the effort to build something like
> > this that it shouldn't be more along the lines of an outpost demo that
>
> > might have a commercial impact rather than a hobbyst project.
>
> In the process of building something commercial, what happens if a great
> sub-commercial opportunity is discovered that directly helps build
> towards commercial-quality code?
>
> The funny thing about Java is that it is a very inaccurate (albeit
> powerful) 'weapon'.  Sun initially aimed Java at the Embedded Market and
> it endedded up hitting the Enterprise market.  Here we initially aimed
> Java at the Enterprise Market (with Enterprise Outpost) and I think
> there is a very good chance that we are going to end up hitting the Home
> Embedded market.
>
> If we go back to the main reason that the Outpost idea was conceived in
> the first place, it was to find a large market for Embedded Java.  This
> overall goal supersedes all lesser goals.  The Embedlets/Outpost project
> was designed to be a vehicle to use to help with this discovery.
>
> From my perspective the project is meeting its purpose excellently
> because I know that I have a much better understanding of Embedded Java
> dynamics than I did when we started this journey back in October.  I now
> think that I have a fairly good grasp of what a good Embedded Java
> opportunity looks like and what the Embedded Java pitfalls look like.
>
>
> We have all put a heck of a lot of work into Embedlets/Embedded Java
> over the past year and now I think it is time for some of that effort to
> pay off.
>
> In my opinion, the Global Light Blinker (GLB) project opens the door to
> the greatest Embedded Java opportunity to come along since the concept
> of Embedded Java was first developed and the Embedded Java community is
> currently the only group on the planet which is in a position to pursue
> it.
>
>
> Here are my reasons for thinking this:
>
> 1) The GLB project shows a large number of people what Embedded Java is
> capable of without having to explain anything to them (the project's
> visibility potential is enormous!).  As soon as they see their lamps
> turning on and off remotely through the internet they will instantly
> 'get it'.
>
> 2) As soon as people's 'lights go on', how long do you think it is going
> to take for them to come up with dozens of ideas for things to control
> inside of the their homes that they can actually use?  How many of these
> people are business people that will instantly see how they can sell
> devices like this to other people?
>
> 3) At this moment in time, the main opportunity for building these
> devices, and showing others how to build them, is being offered to the
> Embedded Java Community (as defined by
> http://embedlets.org/images/flounder.jpg). The Embedded Java developers
> represent the primary Community in the world that has the correct mix of
> Hardware/Software skills needed to build these devices.
>
> 4) The great thing for us is that the 'remote control of in-home
> devices' opportunity is in its very early stages because NAT has been an
> effective roadblock which has prevented it from materializing.  JXTA 2.0
> smashed this roadblock a few months ago and now, very suddenly, the
> Embedded Java Community has *secure* access into the home.  To get
> started, we don't need commercial-quality hardware or a finished and
> commercial-quality Embedlets implementation.  As incomplete as it is,
> the Embedlets implementation that we currently have is more than ready
> for starting to pursue this opportunity.
>
>
> To summarize, the Enterprise Outpost idea is a great idea, and we are
> slowly getting there. In the process of building the Enterprise Outpost
> the Home Device Outpost was discovered, and it has a large market that
> we can pursue right now.
>
>
>
> > The other thing we need to be careful of is not to dilute our efforts
> > to such an extent that progress stalls.
>
> I would say that progress on Embedlets is about to make a great leap
> forward.
> When viewed from the right perspective, a number of seemingly
> disconnected efforts can be seen to actually be part of a
> well-coordinated effort.  Some people's style when building a system is
> to work sequentially and to completely finish the current component
> before moving on to the next step.
>
> A style that contrasts this is to work on all of the components in
> parallel so that the quality of the interfaces between the components
> can be maximized and also so that the system can be better tuned to fit
> its overall purpose.
>
> I am definitely a parallel-development-style person so perhaps this
> knowledge might ease your concerns a bit.
>
>
>
> Anyway, for the past couple of weeks I have been working 'like a dog' to
> get my mind around JXTA 2.0 with the goal of remotely blinking a house
> lamp which is sitting behind NAT in someone's home.  I am so close now
> that I can 'almost taste it' and with any luck the first LightBlinker
> should go live sometime this weekend.
>
> I have also already found a company that is willing to make the beta
> hardware and I even convinced them to hire our University students to do
> the assembly.
> The hardware specification is going to be open so that anyone can
> implement them but it is my guess that most people would rather just buy
> a reasonably priced pre-assembled box.
>
>
> But actually, the LightBlinker project is just a proof of concept, the
> real opportunity is in meeting the demand for all of the other things
> that people want to monitor and control in their homes.
>
>
> So, is anyone here interested in this idea enough to discuss it further?
>
>
> Ted
>
> __________________________________
> Do you Yahoo!?
> SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com
>
>
> -------------------------------------------------------
> This SF.Net email sponsored by: Free pre-built ASP.NET sites including
> Data Reports, E-commerce, Portals, and Forums are available now.
> Download today and enter to win an XBOX or Visual Studio .NET.
> http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01
> _______________________________________________
> Embedlets-developer mailing list
> Emb...@li...
> https://lists.sourceforge.net/lists/listinfo/embedlets-developer
>
>
>
>
>
> -------------------------------------------------------
> This SF.Net email sponsored by: Free pre-built ASP.NET sites including
> Data Reports, E-commerce, Portals, and Forums are available now.
> Download today and enter to win an XBOX or Visual Studio .NET.
> http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01
> _______________________________________________
> Embedlets-developer mailing list
> Emb...@li...
> https://lists.sourceforge.net/lists/listinfo/embedlets-developer
>

RE: [Embedlets-dev] Global Light Blinker Project proposal

[Ted K. <tk...@ya...>]

Chris wrote:

> My experience in the lighting control business is actually quite extensive.
> In the early 90's I designed a system to run the lighting for large
> commercial buildings. Based on the Intel 8051 and the twisted wire BitBus
> network we were able to control buildings with up to 250 networked panels
> each controlling 255 light circuits. This was installed in the tallest
> building in Los Angeles, the Library Square. (The one that they 'fried' in
> the movie Indepdenance Day) and many others around the country.

Man Chris, the amount of embedded systems experience that you have never ceases
to amaze me!  How many total watts of power was this system controlling?



> My point to this is that there is also a large market to efficiently manage
> the energy consumption in commercial buildings, especially with a system
> that would not require rewiring existing  buildings.
> 
> The issues are similar to those in the home (security, ease of installation,
> remote management etc.) but also involve tieing in to the tenant management
> and billing systems as well.

Ok, here is a question for you then.  I think that as soon as people and
companies see how easy it is to remotely and securely control any device, or
groups of devices (from 1 up to potentially billions, the JXTA address space is
astounding), behind or not behind firewalls and NATs, that they are going to
want to engage the services of the people who can build this stuff for them.

How are we (the Embedded Java Developer Community) going to meet this demand in
an organized manner if it materializes?  It seems to me that having something
like an Embedded Java commercial website that matches up companies who want
these kind of devices with the people and companies that can make them, is
going to be needed.


Ted

__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com

RE: [Embedlets-dev] Global Light Blinker Project proposal

[Ted K. <tk...@ya...>]

James wrote:

> Well done.. It's a very good point that you don't always hit the target
> you are aiming for.. I am impressed that you have got so far as to have
> a manufacturer and working model which is driving your confidence.

Hey, it did not take much selling either.  All I had to do was to tell them
that a person could securely control or monitor anything inside their Home from
out on the internet using a cell phone, any PC or even a Web Browser and they
just instantly 'got it'.



> I must admit I am not paying as much attention as I should be. So this
> idea is to allow Home automation meaning people can connect to their
> homes webbrowser and turn lights on and off?

Close.  A webbrowser is not involved and the lights are just for the proof of
concept.  We can control anything in the home that can be interfaced to.  All
that is needed is to have one or more JXTA Peers running inside of the house
that are part of the person's personal PeerGroup.  JXTA 2.0 has already
implemented encrypted TLS (Transport Layer Security) along with encrypted
authentication for peer group access and communications.  The JXTA groups has
solved many of the tough communications problems that we have been struggling
with for the past year.

Each JXTA peer in the peer group has a universal unique ID (UUID) which means
that we can give any device in the home a UUID and then monitor and control it
from anywhere in the world.  The really great thing is that there is not
central UUID authority and so anyone is free to create as many UUIDs as they
need.



> BTW - for the dummies.. What is NAT?

Network Address Translation.  It is the main mechanism used to extend the
present limited IPV4 address space by taking a routable IP address and then
serving non-routable 'dummy' IP addresses to devices in a domain that then all
share this one routable address.

In most people's homes (and probably in most business to) a NAT box (like the
one that an ISP cable company installs) will serve dummy address to any device
in the home that needs one and when the device wants to go out to the internet
it makes a request to the NAT box and the NAT box places the dummy IP address,
and the destination IP address, in an intenal lookup table and then resends the
request to the destination IP address using the one routable IP address that it
has.

When the response comes back the NAT box looks in its lookup table to match the
response to the request and then it resends the response to the internal
originating device using its dummy IP address.

The big problem with monitoring and controlling devices in the home up to this
point has been the following:  When an incoming IP packet comes into the NAT
box, and it was not the result of an outgoing request, then there is no match
in the NAT's lookup table and the message gets dumped into the bit bucket.

JXTA 2.0 just solved this 'punching through the NAT' problem a couple of months
ago and so they have just opened the remote home device control market wide
open for anyone who knows both Java and Embedded systems.

BTW, JXTA also punches through firewalls...


James, it gets even better...  The JXME sub-project has also created technology
that allows a full JXTA peer to act as a proxy for very small devices that can
only communicate using HTTP.  Because of this I think that your uVMs, along
with all of the Systronix products, are in a perfect position to fill this
amazing market opportunity.


Ted

PS, I have just succeeded in creating an experimental GlobalLightBlinker JXTA
Peer Group and the next step is to write a small LightBlink test application
and build a lamp controller box (with the parts that came in yesterday).  I
have already lined up someone who has a NAT connection to the internet in their
home to test the box and as soon as everything is ready I am going to jump on
my bike and ride over there (probably at a rate which is way over the speed
limit ;-)

 

__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com

RE: [Embedlets-dev] Global Light Blinker Project proposal

[James C. <ca...@vi...>]

>The JXME sub-project has also created technology that allows a full 
>JXTA peer to act as a proxy for very small devices that can only 
>communicate using HTTP.  Because of this I think that your uVMs,..

Yep.. I remember going through JXTA a while back and thinking about if I
wanted to put into into a uVM but decided HTTP with a proxy was the
better choice because I always thought there would have to be at least 1
'heavyweight' (relative to uVM) conduit into the real-world. Having a
JXTA proxy with the SLIP JAPL HTTP remoting stack we talked about before
is looking really interesting. Boy.. The more I get into it HTTP for uVM
with the Java Servlet container is really turning out to be a great
choice.. Very happy with the combination of applications that are coming
from it!


OK.. Hmm.. I am going to do a rapid think tank on this because I am
RIGHT NOW writing my muvium Bible 'Technology Evaluation' document that
encapsulates everything about muvium and the emerging connectivity
application space, heirachial java /outpost, generic user interfaces via
irda enabled PDA/MobilePhone/Gameboy browsers, WindowCE.NET
connectivity/Industrial control etc. Plus where and why muvium 'makes it
possible'

This document I have about 2 days before it has to hit the printers
before and will be placed into the hot little hands of 1000 world class
embedded engineers and many top Embedded companies, in a workshop think
tank environment and need to know what to 'sell'.. 

Could be good timing. (more good timing)

New Section: JXTA Emerges.

Ted, can you put together in as condensed a form as possible your best
language on why JXTA is great and why this is a great space for java to
help me build this new section in this what is turning out to be a very
powerful document on the future of java embedded application space.

More soon,

James Caska
www.muvium.com
uVM - 'Java Bred for Embedded'



-----Original Message-----
From: emb...@li...
[mailto:emb...@li...] On Behalf Of
Ted Kosan
Sent: Saturday, 5 July 2003 2:58 AM
To: emb...@li...
Subject: RE: [Embedlets-dev] Global Light Blinker Project proposal


Topic tags:[ARCH][JAPL][WIRING][DOCS][MGMT][STRATEGY][NEWBIE]
_______________________________________________

James wrote:

> Well done.. It's a very good point that you don't always hit the 
> target you are aiming for.. I am impressed that you have got so far as

> to have a manufacturer and working model which is driving your 
> confidence.

Hey, it did not take much selling either.  All I had to do was to tell
them that a person could securely control or monitor anything inside
their Home from out on the internet using a cell phone, any PC or even a
Web Browser and they just instantly 'got it'.



> I must admit I am not paying as much attention as I should be. So this

> idea is to allow Home automation meaning people can connect to their 
> homes webbrowser and turn lights on and off?

Close.  A webbrowser is not involved and the lights are just for the
proof of concept.  We can control anything in the home that can be
interfaced to.  All that is needed is to have one or more JXTA Peers
running inside of the house that are part of the person's personal
PeerGroup.  JXTA 2.0 has already implemented encrypted TLS (Transport
Layer Security) along with encrypted authentication for peer group
access and communications.  The JXTA groups has solved many of the tough
communications problems that we have been struggling with for the past
year.

Each JXTA peer in the peer group has a universal unique ID (UUID) which
means that we can give any device in the home a UUID and then monitor
and control it from anywhere in the world.  The really great thing is
that there is not central UUID authority and so anyone is free to create
as many UUIDs as they need.



> BTW - for the dummies.. What is NAT?

Network Address Translation.  It is the main mechanism used to extend
the present limited IPV4 address space by taking a routable IP address
and then serving non-routable 'dummy' IP addresses to devices in a
domain that then all share this one routable address.

In most people's homes (and probably in most business to) a NAT box
(like the one that an ISP cable company installs) will serve dummy
address to any device in the home that needs one and when the device
wants to go out to the internet it makes a request to the NAT box and
the NAT box places the dummy IP address, and the destination IP address,
in an intenal lookup table and then resends the request to the
destination IP address using the one routable IP address that it has.

When the response comes back the NAT box looks in its lookup table to
match the response to the request and then it resends the response to
the internal originating device using its dummy IP address.

The big problem with monitoring and controlling devices in the home up
to this point has been the following:  When an incoming IP packet comes
into the NAT box, and it was not the result of an outgoing request, then
there is no match in the NAT's lookup table and the message gets dumped
into the bit bucket.

JXTA 2.0 just solved this 'punching through the NAT' problem a couple of
months ago and so they have just opened the remote home device control
market wide open for anyone who knows both Java and Embedded systems.

BTW, JXTA also punches through firewalls...


James, it gets even better...  The JXME sub-project has also created
technology that allows a full JXTA peer to act as a proxy for very small
devices that can only communicate using HTTP.  Because of this I think
that your uVMs, along with all of the Systronix products, are in a
perfect position to fill this amazing market opportunity.


Ted

PS, I have just succeeded in creating an experimental GlobalLightBlinker
JXTA Peer Group and the next step is to write a small LightBlink test
application and build a lamp controller box (with the parts that came in
yesterday).  I have already lined up someone who has a NAT connection to
the internet in their home to test the box and as soon as everything is
ready I am going to jump on my bike and ride over there (probably at a
rate which is way over the speed limit ;-)

 

__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com


-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01
_______________________________________________
Embedlets-developer mailing list
Emb...@li...
https://lists.sourceforge.net/lists/listinfo/embedlets-developer

RE: [Embedlets-dev] Global Light Blinker Project proposal

[Ted K. <tk...@ya...>]

James wrote:

> Boy.. The more I get into it HTTP for uVM
> with the Java Servlet container is really turning out to be a great
> choice.. Very happy with the combination of applications that are coming
> from it!

It looks like your technology instincts are proving to be very good!  JXTA
actually uses a servlet container too (Jetty) in order to handle all of its
HTTP needs.



> Ted, can you put together in as condensed a form as possible your best
> language on why JXTA is great and why this is a great space for java to
> help me build this new section in this what is turning out to be a very
> powerful document on the future of java embedded application space.

No problem!  About how many pages would you like it to be?


In the mean time, this short JXTA executive overview should serve to refresh
your memory on JXTA:

http://www.jxta.org/project/www/docs/JXTA-Exec-Brief-032803.pdf


Ted

__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com

RE: [Embedlets-dev] Global Light Blinker Project proposal

[James C. <ca...@vi...>]

Thanks Ted,

No more than 2 pages.. Possibly even just 1.. This is a
marketing/technology vision Document that needs to 'hit between the
eyes' what you can do with the technology and squeezes out the most
compelling thing about the solution. It is as much for the engineers as
it is for potential investors which is a place I may go soon ;-)

Where muvium sits with JXTA here is the same place as it is sitting with
all the rest.. It is the real-time end point with a proxy talking to one
or more uVM devices over simple serial over a serial link (insert
transport here - irda, wired, radio, X-10, zigbee) 

Be it .NET, J2ME, JXTA, internet directly, WinSOCK, outpost.. It's all
the same pattern..

Must say writing this document is both exhausting and exciting!..
Producing this sort of stuff is incredibly hard I have discovered, but
as I read it and look at the pretty pictures I am getting darn excited
as the paradigm shift of embedded with internet connectivity is being
revealed before my very eyes.

James Caska
www.muvium.com
uVM - 'Java Bred for Embedded'



-----Original Message-----
From: emb...@li...
[mailto:emb...@li...] On Behalf Of
Ted Kosan
Sent: Saturday, 5 July 2003 5:01 AM
To: emb...@li...
Subject: RE: [Embedlets-dev] Global Light Blinker Project proposal


Topic tags:[ARCH][JAPL][WIRING][DOCS][MGMT][STRATEGY][NEWBIE]
_______________________________________________

James wrote:

> Boy.. The more I get into it HTTP for uVM
> with the Java Servlet container is really turning out to be a great 
> choice.. Very happy with the combination of applications that are 
> coming from it!

It looks like your technology instincts are proving to be very good!
JXTA actually uses a servlet container too (Jetty) in order to handle
all of its HTTP needs.



> Ted, can you put together in as condensed a form as possible your best

> language on why JXTA is great and why this is a great space for java 
> to help me build this new section in this what is turning out to be a 
> very powerful document on the future of java embedded application 
> space.

No problem!  About how many pages would you like it to be?


In the mean time, this short JXTA executive overview should serve to
refresh your memory on JXTA:

http://www.jxta.org/project/www/docs/JXTA-Exec-Brief-032803.pdf


Ted

__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com


-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01
_______________________________________________
Embedlets-developer mailing list
Emb...@li...
https://lists.sourceforge.net/lists/listinfo/embedlets-developer

RE: [Embedlets-dev] 1 page JXTA paper for James

[Ted K. <tk...@ya...>]

Ok James, here is the paper.  I tried to make it as non-technical as possible
while still getting across the main ideas.  Hope it helps...

Ted

------

Managing billions of Internet-connected Embedded devices using JXTA and Java.

BILLIONS OF GENERIC NETWORK NODES

JXTA (www.jxta.org) is a new networking technology that allows any devices that
can be connected to the Internet to be treated as generic network nodes which
developers can form into subgroups.  These JXTA subgroups are a new class of
computer, called a “network-based computer”, and developers can dynamically
create these network-based computers out of generic JXTA nodes in order to
solve domain-specific problems.  JXTA technology is designed to scale to
billions of nodes and these nodes can consist of any devices which have
electronic “heart beats”, like PCs, cell phones, servers, PDAs and embedded
systems.


THE NETWORK *IS* THE COMPUTER

One way to look at how the new network-based development works is as follows. 
In the “old” days, the computer use to be the computer and in order to tailor a
computer's capabilities for a given application, one would plug cards into the
computer's ISA or PCI buses.  For example, in order to control a servo motor
system, one would plug a servo motor controller card into a PCI slot and then
the computer's operating system would recognize it and make it available to
software applications.

But now, instead of the computer being the computer, the *network* is the
computer and these new network-based computers consist of nodes connected by
wired or wireless network connections.  These networked nodes can be as close
to one another as fractions of a millimeter or as far apart from one another as
the other side of the globe.  In order to expand the capabilities of a
network-based computer, one simply plugs more nodes into the network.  One way
of looking at this is that the network is the PCI buss for the new class of
network-based computers.


JAVA IS AN OPERATING SYSTEM FOR NETWORK-BASED COMPUTERS

Just like Linux and Windows are operating systems for single computers, Java is
an operating system for network-based computers.  As with all paradigm shifts,
this is a difficult thing to see at first but as people start using these new
network-based computers the understanding of them and their potential will
eventually 'sink in'.

Here are some exciting application scenarios that the new network-based
computers have recently enabled:

1)  Secure remote control and monitoring of devices within the home or business
using any PC on the internet or a cell phone.  Service companies can also be
contracted to provide remote in-home services such as security, appliance
monitoring and energy management.

2)  Company-wide automated 6-Sigma data measurement applications which feed
measurement data into the company's enterprise systems.

3)  City-wide air conditioning load management system.

4)  Quick configuration of CIM (Computer Integrated Manufacturing) workcells
for the flexible production of parts.

__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com

RE: [Embedlets-dev] 1 page JXTA paper for James

[James C. <ca...@vi...>]

Thanks! Ted.. 

Just what I needed.. Now to do (another) pretty picture and integrate
into the doc.. 

BTW - Is there an equivalent technology to JXTA from the Microsoft .NET
croud? 

James Caska
www.muvium.com
uVM - 'Java Bred for Embedded'



-----Original Message-----
From: emb...@li...
[mailto:emb...@li...] On Behalf Of
Ted Kosan
Sent: Saturday, 5 July 2003 10:13 PM
To: emb...@li...
Subject: RE: [Embedlets-dev] 1 page JXTA paper for James


Topic tags:[ARCH][JAPL][WIRING][DOCS][MGMT][STRATEGY][NEWBIE]
_______________________________________________

Ok James, here is the paper.  I tried to make it as non-technical as
possible while still getting across the main ideas.  Hope it helps...

Ted

------

Managing billions of Internet-connected Embedded devices using JXTA and
Java.

BILLIONS OF GENERIC NETWORK NODES

JXTA (www.jxta.org) is a new networking technology that allows any
devices that can be connected to the Internet to be treated as generic
network nodes which developers can form into subgroups.  These JXTA
subgroups are a new class of computer, called a "network-based
computer", and developers can dynamically create these network-based
computers out of generic JXTA nodes in order to solve domain-specific
problems.  JXTA technology is designed to scale to billions of nodes and
these nodes can consist of any devices which have electronic "heart
beats", like PCs, cell phones, servers, PDAs and embedded systems.


THE NETWORK *IS* THE COMPUTER

One way to look at how the new network-based development works is as
follows. 
In the "old" days, the computer use to be the computer and in order to
tailor a computer's capabilities for a given application, one would plug
cards into the computer's ISA or PCI buses.  For example, in order to
control a servo motor system, one would plug a servo motor controller
card into a PCI slot and then the computer's operating system would
recognize it and make it available to software applications.

But now, instead of the computer being the computer, the *network* is
the computer and these new network-based computers consist of nodes
connected by wired or wireless network connections.  These networked
nodes can be as close to one another as fractions of a millimeter or as
far apart from one another as the other side of the globe.  In order to
expand the capabilities of a network-based computer, one simply plugs
more nodes into the network.  One way of looking at this is that the
network is the PCI buss for the new class of network-based computers.


JAVA IS AN OPERATING SYSTEM FOR NETWORK-BASED COMPUTERS

Just like Linux and Windows are operating systems for single computers,
Java is an operating system for network-based computers.  As with all
paradigm shifts, this is a difficult thing to see at first but as people
start using these new network-based computers the understanding of them
and their potential will eventually 'sink in'.

Here are some exciting application scenarios that the new network-based
computers have recently enabled:

1)  Secure remote control and monitoring of devices within the home or
business using any PC on the internet or a cell phone.  Service
companies can also be contracted to provide remote in-home services such
as security, appliance monitoring and energy management.

2)  Company-wide automated 6-Sigma data measurement applications which
feed measurement data into the company's enterprise systems.

3)  City-wide air conditioning load management system.

4)  Quick configuration of CIM (Computer Integrated Manufacturing)
workcells for the flexible production of parts.

__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com


-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01
_______________________________________________
Embedlets-developer mailing list
Emb...@li...
https://lists.sourceforge.net/lists/listinfo/embedlets-developer

RE: [Embedlets-dev] 1 page JXTA paper for James

[Ted K. <tk...@ya...>]

James wrote:

> BTW - Is there an equivalent technology to JXTA from the Microsoft .NET
> croud? 

Not that I am aware of.  I think that one of .NET's main weaknesses is that it
was not designed to be a general purpose network-centric technology like Java
was and I think that this is going to be a major problem for Microsoft going
forward.

At its core, though, JXTA is just an open protocol specification that can be
implemented in any language and it is not specifically related to Java at all.

Somehow I do not see Microsoft implementing it any time soon however...


Ted

__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com

RE: [Embedlets-dev] 1 page JXTA paper for James

[James C. <ca...@vi...>]

Interesting.

Probably really easy though.. Load up the java to C# translator and
implement a few low level routines..

James Caska
www.muvium.com
uVM - 'Java Bred for Embedded'



-----Original Message-----
From: emb...@li...
[mailto:emb...@li...] On Behalf Of
James Caska
Sent: Sunday, 6 July 2003 3:46 AM
To: emb...@li...
Subject: RE: [Embedlets-dev] 1 page JXTA paper for James


Topic tags:[ARCH][JAPL][WIRING][DOCS][MGMT][STRATEGY][NEWBIE]
_______________________________________________

Thanks! Ted.. 

Just what I needed.. Now to do (another) pretty picture and integrate
into the doc.. 

BTW - Is there an equivalent technology to JXTA from the Microsoft .NET
croud? 

James Caska
www.muvium.com
uVM - 'Java Bred for Embedded'



-----Original Message-----
From: emb...@li...
[mailto:emb...@li...] On Behalf Of
Ted Kosan
Sent: Saturday, 5 July 2003 10:13 PM
To: emb...@li...
Subject: RE: [Embedlets-dev] 1 page JXTA paper for James


Topic tags:[ARCH][JAPL][WIRING][DOCS][MGMT][STRATEGY][NEWBIE]
_______________________________________________

Ok James, here is the paper.  I tried to make it as non-technical as
possible while still getting across the main ideas.  Hope it helps...

Ted

------

Managing billions of Internet-connected Embedded devices using JXTA and
Java.

BILLIONS OF GENERIC NETWORK NODES

JXTA (www.jxta.org) is a new networking technology that allows any
devices that can be connected to the Internet to be treated as generic
network nodes which developers can form into subgroups.  These JXTA
subgroups are a new class of computer, called a "network-based
computer", and developers can dynamically create these network-based
computers out of generic JXTA nodes in order to solve domain-specific
problems.  JXTA technology is designed to scale to billions of nodes and
these nodes can consist of any devices which have electronic "heart
beats", like PCs, cell phones, servers, PDAs and embedded systems.


THE NETWORK *IS* THE COMPUTER

One way to look at how the new network-based development works is as
follows. 
In the "old" days, the computer use to be the computer and in order to
tailor a computer's capabilities for a given application, one would plug
cards into the computer's ISA or PCI buses.  For example, in order to
control a servo motor system, one would plug a servo motor controller
card into a PCI slot and then the computer's operating system would
recognize it and make it available to software applications.

But now, instead of the computer being the computer, the *network* is
the computer and these new network-based computers consist of nodes
connected by wired or wireless network connections.  These networked
nodes can be as close to one another as fractions of a millimeter or as
far apart from one another as the other side of the globe.  In order to
expand the capabilities of a network-based computer, one simply plugs
more nodes into the network.  One way of looking at this is that the
network is the PCI buss for the new class of network-based computers.


JAVA IS AN OPERATING SYSTEM FOR NETWORK-BASED COMPUTERS

Just like Linux and Windows are operating systems for single computers,
Java is an operating system for network-based computers.  As with all
paradigm shifts, this is a difficult thing to see at first but as people
start using these new network-based computers the understanding of them
and their potential will eventually 'sink in'.

Here are some exciting application scenarios that the new network-based
computers have recently enabled:

1)  Secure remote control and monitoring of devices within the home or
business using any PC on the internet or a cell phone.  Service
companies can also be contracted to provide remote in-home services such
as security, appliance monitoring and energy management.

2)  Company-wide automated 6-Sigma data measurement applications which
feed measurement data into the company's enterprise systems.

3)  City-wide air conditioning load management system.

4)  Quick configuration of CIM (Computer Integrated Manufacturing)
workcells for the flexible production of parts.

__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com


-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01
_______________________________________________
Embedlets-developer mailing list
Emb...@li...
https://lists.sourceforge.net/lists/listinfo/embedlets-developer





-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01
_______________________________________________
Embedlets-developer mailing list
Emb...@li...
https://lists.sourceforge.net/lists/listinfo/embedlets-developer