Re: [Embedlets-dev] What wld be the relation between Outpost & Savant ?
Status: Alpha
Brought to you by:
tkosan
From: Ted K. <tk...@ya...> - 2004-03-02 07:22:36
|
Ramesh wrote: > Just wondering.. what would be the relationship between Outpost > container and Savant? Would Outpost be a possible implementation layer > for Savant? Or, would outpost feed into Savant- as an intermediary > between the devices and Savant? An 'Enterprise Outpost' was conceived to be an open 'black-box' Internet-connected computer platform that is specifically designed to be easily interface to a company's physical processes and also easily integrated with its backend enterprise systems. The idea is to allow backend Enterprise systems to monitor and control all aspects of a company's physical processes through the use of standardized 'black boxes' that embody standardized embedded software and hardware components. As part of this process, this group developed what we call Embedlets (embedded system software components, think servlets for embedded systems) and an Embedlet Container to run them in in order to help achieve this goal. Another goal that we have is to enable Outposts to be easily managed and re-configured in the field so that their numbers can be scaled up into the thousands. Given this definition of an Enterprise Outpost, I see an RFID Savant server as being a software system that simply runs on an Outpost. The Outpost black-box computer would be directly interfaced to an RFID reader and it would then host the Savant software. In addition to this, the Outpost would provide the capability to interface to other physical things around the Outpost along with providing the ability for the whole system to be managed remotely. This group now has the ability to make at least an alpha-level version of these Enterprise Outposts but now we are at a point where we need to partner with a community of J2EE developers to help evolve the technology. > While Outpost is an implementation platform for any apps involving > devices, may accelerate adoption if we can have a clear articulation > for RFID based solutions? I agree with this completely. Our group of Embedded Java developers has been in need of an embedded systems related problem that the J2EE community needed help solving and it appears that RFID meets this requirement very well. At this point, it appears that no one knows exactly what the main RFID-oriented problems and best-practice solutions are going to be and this is why I think that an open, experimental RFID project (like the proposed one involving TSS members) would be useful in starting to figure things like this out. We can handle the hardware and embedded software aspects of an open project like this if we could get a group of J2EE developers to handle its Enterprise Software aspects. Ted __________________________________ Do you Yahoo!? Yahoo! Search - Find what youre looking for faster http://search.yahoo.com |