You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "bneradt (via GitHub)" <gi...@apache.org> on 2023/05/12 20:08:38 UTC
[GitHub] [trafficserver] bneradt opened a new issue, #9705: Create .so file(s) with symbol definitions for the plugin API
bneradt opened a new issue, #9705:
URL: https://github.com/apache/trafficserver/issues/9705
it would be helpful to have the symbols declared in `include/ts` built into a separate .so file (or maybe files) for its definitions rather than having them all defined in traffic_server.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@trafficserver.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [trafficserver] bryancall commented on issue #9705: Create .so file(s) with symbol definitions for the plugin API
Posted by "bryancall (via GitHub)" <gi...@apache.org>.
bryancall commented on issue #9705:
URL: https://github.com/apache/trafficserver/issues/9705#issuecomment-1645958849
@jpeach What is the issue of resolving the symbols that are in the traffic_server binary that the API DSO depends on?
I wrote up and example of how this would work: https://github.com/bryancall/plugin_dso
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@trafficserver.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [trafficserver] jpeach commented on issue #9705: Create .so file(s) with symbol definitions for the plugin API
Posted by "jpeach (via GitHub)" <gi...@apache.org>.
jpeach commented on issue #9705:
URL: https://github.com/apache/trafficserver/issues/9705#issuecomment-1548843362
I see. IIUC, if you actually separate the API symbols into a different DSO, then all their dependencies would either need to be in that DSO, or resolved from the `traffic_server` binary. Neither sounds ideal, unfortunately.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@trafficserver.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [trafficserver] jpeach commented on issue #9705: Create .so file(s) with symbol definitions for the plugin API
Posted by "jpeach (via GitHub)" <gi...@apache.org>.
jpeach commented on issue #9705:
URL: https://github.com/apache/trafficserver/issues/9705#issuecomment-1546793088
>
> it would be helpful to have the symbols declared in `include/ts` built into a separate .so file (or maybe files) for its definitions rather than having them all defined in traffic_server.
What would be the use case for that?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@trafficserver.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [trafficserver] bneradt commented on issue #9705: Create .so file(s) with symbol definitions for the plugin API
Posted by "bneradt (via GitHub)" <gi...@apache.org>.
bneradt commented on issue #9705:
URL: https://github.com/apache/trafficserver/issues/9705#issuecomment-1546763891
Zhengxi Li is currently looking into implementing this, but we cannot officially assign him because he is not a committer yet. I'll assign myself as a proxy.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@trafficserver.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [trafficserver] bneradt commented on issue #9705: Create .so file(s) with symbol definitions for the plugin API
Posted by "bneradt (via GitHub)" <gi...@apache.org>.
bneradt commented on issue #9705:
URL: https://github.com/apache/trafficserver/issues/9705#issuecomment-1548709675
> >
>
> > it would be helpful to have the symbols declared in `include/ts` built into a separate .so file (or maybe files) for its definitions rather than having them all defined in traffic_server.
>
> What would be the use case for that?
Presently, the InkAPI symbols are all linked in directly to the traffic_server binary, so plugins have no .so to link against and verify symbols against. It would be handy to have an .so for plugins to link against.
@bryancall has also seen binary compatibility issues in registers across minor releases that we're hoping the compiler will not produce if the symbols are built into a library.
There is a plan to discuss this further in the summit either tomorrow or the next day.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@trafficserver.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org