[csw-maintainers] Proposal: direct binding for all the opencsw software stack

[Yann Rouillard]

I can think of a case where it would be a problem with plugin but I don't
know if it's a real life case.

If the plugin needs some symbols from the binary loading it (for exemple
the binary provides some API to the plugin) and if a plugin can be loaded
by different binary, I suppose that would be a problem because the plugin
will only try to bind against the binary it was linked with at compilation
time.

I also wonder if direct binding works well with auxiliary filters (
http://docs.oracle.com/cd/E19683-01/816-1386/chapter4-5/index.html ), it is
another linker feature that has been used in the neon package to be able to
provide an alternative neon library with more feature. It would be
interesting to have neon in the test package set.

Yann

2012/8/25 Ben Walton <bwalton at opencsw.org>

> Excerpts from Ben Walton's message of Fri Aug 24 15:04:16 -0400 2012:
>
> > runtime binding).  The only case I could think of where that would
> > be desirable behaviour is in something that dlopen()'s multiple
> > objects for a plugin system where one plugin could redefine an
> > interface and a second plugin could re-redefine it and so on.  It's
> > like that there are other cases where it _might_ be desirable
> > behaviour but I have to think it's by far the minority.
>
> This isn't even valid.  I'm not sure where I was going with that.
> dlopen()'d things wouldn't be directly applicable here.  I can't think
> of a case where something would prefer the current behaviour if given
> direct linking as an option.  There is likely something that does care
> but as long as we can disable in that case, I think direct linking is
> definitely the way to go.
>
> Thanks
> -Ben
> --
> Ben Walton
> Systems Programmer - CHASS
> University of Toronto
> C:416.407.5610 | W:416.978.4302
>
> _______________________________________________
> maintainers mailing list
> maintainers at lists.opencsw.org
> https://lists.opencsw.org/mailman/listinfo/maintainers
> .:: This mailing list's archive is public. ::.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opencsw.org/pipermail/maintainers/attachments/20120825/0364587b/attachment-0001.html>