RE: [Vcb-framework] ModelConfig internal structure

[<Hov...@ly...>]

The main question is how to make access fast. So some indexing maybe needed.
Any idea?

Hovhannes

-----Original Message-----
From: arto [mailto:art...@ed...]
Sent: Wednesday, April 30, 2003 12:09 PM
To: Hov...@ly...
Subject: Re: [Vcb-framework] ModelConfig internal structure


Yes we have new ModelConfig sequence which is in the CVS

Concerning Model Config storage structure:

1. For running purpose we need to keep only link collection of the
configuration and processing links is fast enough.

2. For visualization and for tracing configuration changes we need several
structures.

1. Device structure: (DeviceInfo) which will have information about
device(name, id, parentID, (maybe userdefinedID), level, terminals, parts
(collection of PartInfo), devices (Collection of DeviceInfo), link
Collection.

2. Part structure: (PartInfo) which will have information about name, id,
parentID, (maybe userdefinedID), level, terminals.

3. Link structure (LinkInfo) which keeps linkID, fromPin and toPin

Do we need LinkInfo?

Do we need userdefinedID for device and part?



 Arto,


----- Original Message -----
From: <Hov...@ly...>
To: <vcb...@li...>
Sent: Wednesday, April 30, 2003 10:32 AM
Subject: [Vcb-framework] ModelConfig internal structure


> Lets discuss Model Config internal storage structure. It is important to
> have fast processing.
>
> Also do you have ready ModelConfig detailed sequence?
>
> Hovhannes
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Vcb-framework mailing list
> Vcb...@li...
> https://lists.sourceforge.net/lists/listinfo/vcb-framework
>