On 8/29/06, Oisin Hurley <[EMAIL PROTECTED]> wrote:
Simon - apologies I've been away from this for the last week...
[deletia]
>> ...and this is why :) There are number of responsibilities of an
>> extension - which you accurately describe - and there are a number
>> of responsibilities of a pl
Simon - apologies I've been away from this for the last week...
[deletia]
...and this is why :) There are number of responsibilities of an
extension - which you accurately describe - and there are a number
of responsibilities of a plugin, related to configuration and
lifecycle
and I think it
On 8/22/06, Oisin Hurley <[EMAIL PROTECTED]> wrote:
Hi Simon,
> Had a long weekend so just picking up this thread. Looks like a really
> useful discussion and I too like the requirement driven approach. I
> have a
> few to add/comment on. It seems that a plugin resolves to a
> component type
>
Hi Simon,
Had a long weekend so just picking up this thread. Looks like a really
useful discussion and I too like the requirement driven approach. I
have a
few to add/comment on. It seems that a plugin resolves to a
component type
or binding, i.e. what the assembly model refers to as extensi
On 8/22/06, Oisin Hurley <[EMAIL PROTECTED]> wrote:
[deletia]
js-d says:
>> > I've been thinking about this and wondering what the architecture
>> > of the runtime will be with many different plugins? Are you guys
>> > envisioning one big process with different (maybe incompatible?)
>> > librari
On 22/08/06, Oisin Hurley <[EMAIL PROTECTED]> wrote:
.
I've seen lots of +1s on this thread, which is nice, and I've just found
out that I can edit the Tuscany wiki, so I'll summarize to there -- the
page will be http://wiki.apache.org/ws/Tuscany/TuscanyCpp/
PluggableCppRuntime
it'll be later t
[deletia]
js-d says:
> I've been thinking about this and wondering what the architecture
> of the runtime will be with many different plugins? Are you guys
> envisioning one big process with different (maybe incompatible?)
> libraries loaded in it? or a more distributed architecture with
> multip
Good stuff here. A couple of comments inline:
On 22/08/06, Oisin Hurley <[EMAIL PROTECTED]> wrote:
> Pete Robbins wrote:
>> Hi Oisin,
>>
>> Here's the dumb question: What do you mean by "Plugin"? Is it a
>> composite or
>> group of composites?
>
> Or just a set of extensions packaged in a libra
Pete Robbins wrote:
Hi Oisin,
Here's the dumb question: What do you mean by "Plugin"? Is it a
composite or
group of composites?
Or just a set of extensions packaged in a library that you plug
into the runtime?
'Plugin' means a piece of software that adds some functionality in the
form o
Hi guys,
I like this requirement based approach, a few +1, comments and questions
below.
Pete Robbins wrote:
Hi Oisin,
Here's the dumb question: What do you mean by "Plugin"? Is it a
composite or
group of composites?
Cheers,
Or just a set of extensions packaged in a library that you pl
Hi Oisin,
Here's the dumb question: What do you mean by "Plugin"? Is it a composite or
group of composites?
Cheers,
On 17/08/06, Oisin Hurley <[EMAIL PROTECTED]> wrote:
Hi guys,
I thought I might kick off a thread on pluggability in the C++
implementation to get some ideas rolling around, so
Hi guys,
I thought I might kick off a thread on pluggability in the C++
implementation to get some ideas rolling around, so while these
are not 'requirements' at all, they might eventually lead to
some ;)
1. Language independence is not an issue here, so all plugins
are described and implemented
12 matches
Mail list logo
