|
| Re: advice in b3 [message #486796 is a reply to message #486668] |
Sat, 19 September 2009 06:17   |
|
On 09/18/2009 04:45 PM, Henrik Lindberg wrote:
> Hi,
> I have been looking at how to handle advice in b3.
>
> In Buckminster advice is available in a CQUERY (advisor nodes), but once
> the query is executed and the components have been materialized, the
> advice is no longer applicable (unless it left side effects in what was
> actually materialized).
>
> Also in Buckminster, the MSPEC is providing advice to materialization.
>
> I would like to have a single advice mechanism in b3. I think it can
> work like this:
>
> - All actions (such as import, invoke, etc.) can specify the advice to
> use. (import advice == Buckminster CQUERY advisor nodes + MSPEC)
> - Advice is specified by using a query mechanism similar to XQuery
> (instead of name pattern in Buckminster advisor nodes and mspec).
> - A piece of advice (advisor), simply needs the result to have a
> suitable interface.
>
> The SAP guys are working on query support for EMF - which seems to be
> useful. Unknown though how far they are, and if they plan a concrete
> query syntax (like XQuery). Does not seem terribly difficult to parse a
> XQuery into the implementation of EMF query.
>
> Advice can then be applied in a much more precise way.
>
> Comments?
> - henrik
Perhaps a generic mechanism like that is too generic? Wouldn't we like to have more control over where advice can be
applied? Perhaps not.
I'm thinking about P2 where you have specific targeted advices like VersionAdvice etc. I was envisioning ActionAdvice
and similar. But perhaps a model query mechanism is what we should build it on.
- thomas
|
|
|
|
| Re: advice in b3 [message #577614 is a reply to message #486668] |
Sat, 19 September 2009 06:17 |
|
On 09/18/2009 04:45 PM, Henrik Lindberg wrote:
> Hi,
> I have been looking at how to handle advice in b3.
>
> In Buckminster advice is available in a CQUERY (advisor nodes), but once
> the query is executed and the components have been materialized, the
> advice is no longer applicable (unless it left side effects in what was
> actually materialized).
>
> Also in Buckminster, the MSPEC is providing advice to materialization.
>
> I would like to have a single advice mechanism in b3. I think it can
> work like this:
>
> - All actions (such as import, invoke, etc.) can specify the advice to
> use. (import advice == Buckminster CQUERY advisor nodes + MSPEC)
> - Advice is specified by using a query mechanism similar to XQuery
> (instead of name pattern in Buckminster advisor nodes and mspec).
> - A piece of advice (advisor), simply needs the result to have a
> suitable interface.
>
> The SAP guys are working on query support for EMF - which seems to be
> useful. Unknown though how far they are, and if they plan a concrete
> query syntax (like XQuery). Does not seem terribly difficult to parse a
> XQuery into the implementation of EMF query.
>
> Advice can then be applied in a much more precise way.
>
> Comments?
> - henrik
Perhaps a generic mechanism like that is too generic? Wouldn't we like to have more control over where advice can be
applied? Perhaps not.
I'm thinking about P2 where you have specific targeted advices like VersionAdvice etc. I was envisioning ActionAdvice
and similar. But perhaps a model query mechanism is what we should build it on.
- thomas
|
|
|
|
Powered by
FUDForum. Page generated in 0.03123 seconds
] 
Search
Help
Register
Login
Home
