Prev: china wholesale nike jordan sneakers WWW.21cn-shoes.COM discount gucci prada puma
Next: Dynamic foreach algorithm
From: shashank on 18 Jan 2008 11:44
On Jan 17, 5:52 pm, liongs...(a)gmail.com wrote:
> On Jan 17, 3:40 am, "H. S. Lahman" <h...(a)pathfindermda.com> wrote:
>
> > > or assemblied with other components.
>
> > Which component concept is that? B-) Alas, component engineering is
> > taking on as many different methodological views as OOA/D.
>
> I read about this from Syperski's "Component Software - Beyond Object
> Oriented Programming" (2003). To be exact on page 174, He mentioned
> and draw a connection between two components C1 and C2.  I can
> understand if they will communicate through a defined interface,
> however my question was how this connection is implemented?

Let me see if I can clarify your doubts at least in context of CORBA
Components.

Lets suppose if we have two component definitions like below

//component 1
component PowerGenerator {
provides Power power_supplier; //Power is an interface

}

and component 2
component VendingMachine {
provides SomeInterface;//another interface
requires Power power_consumer;
}

Now if we connect power_consumer port of VendingMachine to
power_supplier port of PowerGenerator, the runtime assembly/deployment
framework of infrastructure takes responsibility of getting reference
of power_supplier (of type Power) from PowerGenerator component and
passing this reference to component VendingMachine.

Both the component implements the published behaviour of providing (in
this case providing reference to Power interface by component
PowerGenerator and accepting reference of type Power by component
VendingMachine. And so that we don't need access to source code/
implementation of both/any components.

This is how it gets implemented.

regards,
Shashank Dutt Jha
From: WALLYWORLD on 18 Jan 2008 12:20
would there be another parenthesis to close the set? I cant see which
publishing refers to the other reference, if that is how it connects ..
but in one direction only the error flags, and other status information
should travel. The operation is tested and then the online status does not
require any more. The controls are contained in the module. All the think
has to do is turn itself off, hopefully.. Yo sanii dai

"shashank" <shashank.dj(a)gmail.com> wrote in message
news:a4ea4214-e2ad-44c9-bc0b-c56be7353f03(a)h11g2000prf.googlegroups.com...
On Jan 17, 5:52 pm, liongs...(a)gmail.com wrote:
> On Jan 17, 3:40 am, "H. S. Lahman" <h...(a)pathfindermda.com> wrote:
>
> > > or assemblied with other components.
>
> > Which component concept is that? B-) Alas, component engineering is
> > taking on as many different methodological views as OOA/D.
>
> I read about this from Syperski's "Component Software - Beyond Object
> Oriented Programming" (2003). To be exact on page 174, He mentioned
> and draw a connection between two components C1 and C2. I can
> understand if they will communicate through a defined interface,
> however my question was how this connection is implemented?

Let me see if I can clarify your doubts at least in context of CORBA
Components.

Lets suppose if we have two component definitions like below

//component 1
component PowerGenerator {
provides Power power_supplier; //Power is an interface

}

and component 2
component VendingMachine {
provides SomeInterface;//another interface
requires Power power_consumer;
}

Now if we connect power_consumer port of VendingMachine to
power_supplier port of PowerGenerator, the runtime assembly/deployment
framework of infrastructure takes responsibility of getting reference
of power_supplier (of type Power) from PowerGenerator component and
passing this reference to component VendingMachine.

Both the component implements the published behaviour of providing (in
this case providing reference to Power interface by component
PowerGenerator and accepting reference of type Power by component
VendingMachine. And so that we don't need access to source code/
implementation of both/any components.

This is how it gets implemented.

regards,
Shashank Dutt Jha


From: hanliong on 19 Jan 2008 02:31
On Jan 19, 3:44 am, shashank <shashank...(a)gmail.com> wrote:
> ..... deleted...
> Now if we connect power_consumer port of VendingMachine to
> power_supplier port of PowerGenerator, the runtime assembly/deployment
> framework of infrastructure takes responsibility of getting reference
> of power_supplier (of type Power) from PowerGenerator component and
> passing this reference to component VendingMachine.

So for CORBA, the connection is done by a runtime assembly/
deployment.
I read few things about CORBA, and seems that they made it clearer
than what .NET proposes.
My research work would be on .NET implementation, so if anyone knows
how would a similar connection be established please let me know.

Regards, Han.
From: hanliong on 19 Jan 2008 02:42
On Jan 19, 10:19 am, "H. S. Lahman" <h...(a)pathfindermda.com> wrote:

> So what has all this got to do with your comments? The main point is
> that Who gets "wired up" is driven by unique rules and policies that are
> probably encapsulated somewhere other than in the client of A or B. If A
> and B are "wired" together, then that is none of the client's business.

Yes, this is my understanding previously. Wiring a component A to B is
not the problem of a client application. However as mentioned by
Shashank if we bought a PowerGenerator component and a VendingMachine
component, and our client application is about a software application
that calculates the selling of items from a Vending machine. Then
this client application should wire PowerGenerator to
VendingMachine.

Anyway, on second thought, you might be right. The wiring should be
done at component developer's site. As this specific wiring is
supposedly beyond client area. Or is it not?

Please enlight me more.

Regards, Han.


From: shashank on 19 Jan 2008 04:00
On Jan 19, 12:31 pm, hanliong <liongs...(a)gmail.com> wrote:
> On Jan 19, 3:44 am, shashank <shashank...(a)gmail.com> wrote:
>
> > ..... deleted...
> > Now if we connect power_consumer port of VendingMachine to
> > power_supplier port of PowerGenerator, the runtime assembly/deployment
> > framework of infrastructure takes responsibility of getting reference
> > of power_supplier (of type Power) from PowerGenerator component and
> > passing this reference to component VendingMachine.
>
> So for CORBA, the connection is done by a runtime assembly/
> deployment.
> I read few things about CORBA, and seems that they made it clearer
> than what .NET proposes.

Yes. It is responsibility of deployment/ assembly infrastructure to
actually make connections.

These connections are specified by application builder/ assembler
using gui based tools or otherwise and is stored in a assembly
descriptor (an xml file) file. This is given as input to assembly
framework that takes care of installing, instantiating and configuring
proper connections and other properties.

regards,
shashank

> My research work would be on .NET implementation, so if anyone knows
> how would a similar connection be established please let me know.
>
> Regards, Han.

First  |  Prev  |  Next  |  Last
Pages: 1 2 3
Prev: china wholesale nike jordan sneakers WWW.21cn-shoes.COM discount gucci prada puma
Next: Dynamic foreach algorithm