[SAGA-RG] Question about saga::attribute and saga::async
Andre Merzky
andre at merzky.net
Tue Aug 21 15:22:18 CDT 2007
Doh!
The rationale behind having saga::attribute implement
saga::async was that, for example for logical files,
attributes are real remote entities, which we should allow
to be handled asynchronously.
But you are right: it does not make sense to have async
methods for metric, job_description etc.
I'm somewhat unsure on how to resolve this cleanly.
One option would be to require async attribute methods on
all classes which implement saga::async. That would be a
convention which would not be reflected in the SIDL spec
though...
Any thoughts?
Cheers, Andre.
Quoting [Ceriel Jacobs] (May 01 2007):
>
> Hi,
>
> I noticed that version 1.0 RC 5 of the SAGA document specifies
> that the saga::attribute interface now implements the saga::async
> interface. I assume that this means that there must be task- and
> async versions of the saga::attribute methods. But this also means
> that several other classes now must implement saga::async (because
> they implement saga::attribute).
> For instance, the class "metric" in
> package saga.monitoring, should that now have async and task
> versions of the add_callback, remove_callback and fire methods?
> I guess not, but since it now implements saga::async, should it?
>
> Ceriel Jacobs
--
"XML is like violence: if it does not help, use more."
More information about the saga-rg
mailing list