This web mail archive is frozen.
This page is part of a frozen web archive of this mailing list.
You can still navigate around this archive, but know that no new mails
have been added to it since July of 2016.
Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.
Jeff Squyres wrote:
> Alternatively, you could do what the ofud BTL does (a currently
> experimental BTL): look for the string "ofud" in the "btl" MCA
> parameter -- i.e., see if the user explicitly asked for the ofud BTL.
> If not found (doing the Right Things with the "^" operator, of
> course), then disable the ofud BTL by returning NULL from the
> component_init() function.
> Either seems fine to me; the ofud method seems a little less elegant
> -- was there a reason not to use exclusivity here? Was it just the
> fact that TCP's exclusivity is already the lowest possible value (0)?
Sorry.. try putting my name in the email or something so I know you're
I think there was but I don't remember right now. If a low exclusivity
for the UD BTL means it won't get used with the RC BTL, then that's
fine. I don't like that string parsing code anyway. Suggestions on
what to set the exclusivity to?