[Openframeworkwg] provider independence
Christoph Lameter
christoph at lameter.com
Tue Dec 10 07:48:10 PST 2013
I think we all agree on these. However, on (3): If my app wants to use
inlining provided by the provider then changes to the provider code would
require recompilation.
On Tue, Dec 10, 2013 at 9:39 AM, Bernard Metzler <BMT at zurich.ibm.com> wrote:
> ...at another level of granularity and hopefully not
> to much off-topic.
>
> Are we all agree on the following requirements
> for the upcoming interface:
>
> (1) must be provider agnostic (well, some providers may only
> implement a subset of functionality, but that is managed
> in a generic way),
> (2) multiple providers can be used from one application
> in parallel,
> (3) changes to provider code does not enforce recompilation
> of the application.
>
> Thanks,
> Bernard.
>
> _______________________________________________
> Openframeworkwg mailing list
> Openframeworkwg at lists.openfabrics.org
> http://lists.openfabrics.org/cgi-bin/mailman/listinfo/openframeworkwg
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openfabrics.org/pipermail/ofiwg/attachments/20131210/bbb9260a/attachment.html>
More information about the ofiwg
mailing list