[frascati] Re: Re: Dynamical creation components and wires

[Lionel Seinturier <Lionel.Seinturier@xxxxxxxxxxxxxx>]

On 08/10/2010 21:27, Sergey Kirgizov wrote:
> On 8 October 2010 18:57, Lionel Seinturier 
> <Lionel.Seinturier@xxxxxxxxxxxxxx 
> <mailto:Lionel.Seinturier@xxxxxxxxxxxxxx>> wrote:
>
>     On 08/10/2010 18:06, kerzolster@xxxxxxxxx
>     <mailto:kerzolster@xxxxxxxxx> wrote:
>
>         My question can seem a little silly, because I have recently
>         started to use SCA and FraSCAti implementation.
>
>         Anyway, Is it a possible to create a lot of (~10 000) components
>         and a lot of
>         wires between them (~100 000)?
>
>     [1] reports on benchmarks which have been done with FraSCAti. Up to
>     13,000 components have been created with FraSCAti in a JVM which was
>     allocated with 64MB of memory. The total number of wires was in the
>     same range than the number of components.
>
> ok, thank you. 
>
>         And how I can create and destroy them at the
>         runtime?
>
>     Before answering this question, let me ask another one, as the
>     answer may differ: what is your starting point for creating these
>     components? Raw component classes? Or .composite XML files in the
>     SCA Assembly Language?
>
> It would be good to create instances of a certain class and connect them 
> in the necessary order.
> Or I can use generated .composite files and load them in runtime, it's 
> not a big problem, I think.
>
> The major point is: at the start I can't know configuration and quantity 
> of necessary components and links.
> The runtime creation, deletion of links and components is very important 
> for me.
> Of course, I want to do it as simple as possible.

You can have a look at [2].

The example illustrates:
* the instantiation of 3 SCA annotated components, 1 composite and 2 
primitives
* the 2 primitives are inserted into the composite
* the composite is bound to the 1st primitive
* the 1st primitive is bound to the 2nd primitive
* 2 properties are set on the 2nd primitive
* the assembly is started
* a service is invoked on the composite
* the invocation goes through the 1st primitive and up to the 2nd one.

More generally, the API for manipulating/introspecting components is 
based on Fractal. More information is available in [3]. You can use the 
API of the BindingController for creating, deleting, querying wires 
(links) between components.

> And, a question:
> Can I use several instances of one class for representing different 
> components?

If you mean "several instances of one class for representing different 
component instances of the same component type", the answer is yes. The 
component factory can be invoked several times with the same class to 
obtain several component instances.

Lionel.

[2] 
http://websvn.ow2.org/listing.php?repname=frascati&path=%2Ftrunk%2Ftinfi%2Fexamples%2Fadvanced%2Fhelloworld-tinfilet%2F
[3] http://fractal.ow2.org/documentation.html

>         Another words, I want to use components like actors
>         (http://en.wikipedia.org/wiki/Actor_model).
>
>
>     Great.
>
>
>         And probably the last question: Somebody did tests with a a
>         large number of
>         of components and communications? What about performance,
>         scalability
>
>
>     As far as I know, no, but in the end this depends a lot on the
>     communication stack that you use to communicate, from intra-JVM
>     local method calls, to remote calls with let say, Apache CXF SOAP
>     Web Services.
>
>
> Well, I will use local and remote method calls for communications.
> And, if it will be possible, I will try to make some tests to measure a 
> perfromance. 
>
> --
> Sergey Kirgizov
> Lip6 

--
Lionel Seinturier
Univ. Lille - Lab. LIFL - INRIA ADAM
http://www.lifl.fr/~seinturi