Re: [foxboro] ArchestrA related question

I don't want to speak for Invensys, (actually I do want to, but they frown 
on it) but I think that the whole ArchestrA magic layer is supposed to let 
you continue to take advantage of things you have installed while allowing 
you to build with newer stuff on top of it.

This could be completely wrong, but let's try a hypothetical example.

Let's say you have an I/A system with an AIN block in version X.3.
Now Invensys creates a newer AIN block in version Y.1 that has a new 
parameter, call it .FUDGE.  Now you bridge the two I/A systems with 
ArchestrA.  The ArchestrA layer would indicate to anything using an 
ArchestrA AIN object that the older one does not contain a true .FUDGE 
parameter, so it might give it some benign default setting, or indicate it 
doesn't exist.  Now you can build your applications, displays, etc. that 
make use of .FUDGE even though the old system doesn't support it. As long 
as you don't try to use it's functionality on the old system everything 
should still work.

At least that's the way I'm understanding ArchestrA at the moment.  It 
would sure be nice to see some of the XML schemas to know if I'm on the 
right path.

Regards,
David
>

"A child of five could understand this. Fetch me a child of five."
         Groucho Marx

 
 
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
 
foxboro mailing list:             http://www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave

Other related posts: