To: J Fieb who wrote (27091 ) 5/24/2000 9:30:00 AM From: J Fieb Respond to of 29386
Here's evidence of what JIRO will do for storage. From the JIRO bb Hello from Melbourne Australia, We are evaluating Jiro as a candidate technology to supply the ?plumbing? behind a new version of our integration product. Things like ORBS, EJBs and Application Servers have been rejected because they are too heavyweight and add prerequisites for potential customers. We?re looking for a lightweight infrastructure we can use to glue the pieces of our product together, relieving us of the stress of writing a distributed networking layer and letting us concentrate on the code that does the actual work. We?d like this infrastructure to supply basic (and extensible) features like transactions, logging and security, so Jiro seems to match our needs nicely. Over the last week I?ve read hundreds of pages on Jiro, Jini, JMX and FMA, and my head is swimming with new acronyms. Some of the terms like ?federation?, ?domain?, ?station?, ?management server?, ?services?, etc are used in overlapping ways that confuse me. I?m having trouble trying to relate Jiro and FMA terms to the proposed structure of our new product. I?ll give you the barest idea of what our product does, then I?ll try to compose some questions. Our product falls into a 3-tier structure -- The low level consists of Java ?drivers? which sit on various machines, their specific job is to suck data in and out of a wide variety of databases and files, transform data and send it in and out of sockets and MQ queues. They do the hard work -- The middle level is a manager that owns a set of drivers on multiple machines that are working together -- The top level is a kind of operator console where the groups of drivers are monitored and controlled. The Jiro model is advertised as being 3-tier: (1) Client (2) Management services (3) Managed resources. This seems to match our product model nicely, but when I look at some sample code (like the StopWatch), I can?t relate what?s happening there to our product. * How do ?stations? and ?services? relate? Does a station contain services? Is a station an actual program or simply an abstract name? * StopWatch is a ?service?, which I thought was the middle tier, so why does it do the actual work that I thought would be done by a bottom tier program? * I thought that bottom tier programs (the Managed resources) had to be written according to a Beans-like convention, but I can?t find any evidence of this. Am I misunderstanding? * Overall, Jiro doesn?t seem to contain a class structure that imposes a 3-tier hierarchy on programmers. I expected sets of classes to support creation of programs that live in each tier, but everything seems to have a ?flat? kind of feel to it. Am I misunderstanding? I?m terribly embarrassed to ask such broad newbie questions, especially if the questions are ill-formed or meaningless. Just ask if you need clarification. I would appreciate any advice or pointers to URLs and articles that might help me get over my acronym and concept confusion. I plan to spend the rest of the day trying to get the StopWatch sample running across two machines, that might help me a bit. Cheers,