-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
请问sandbox可以支持用户自定添加transformer吗 #411
Labels
Comments
回答问题:没有 如果你真需要做这种个性化的定制,这个项目也是开源的,可以考虑fork自己修改。不过我认为ByteBuddy可能会是你更好的选择。 |
好的多谢,另外问下sandbox有对threadlocal父子线程传递的方案吗,特别是forkjoin场景,似乎只用aop好像不能实现吧? |
使用ttl的agent又似乎要多引入一个agent |
线程间上下文传递和AOP无关,主要出现是一些代码调用联跟踪的场景,不支持的原因还是想尽量保证sandbox功能的纯粹。我们实际写的时候的确会有遇到类似的问题,我的常规处理做法是用一个全局的WeakMap来解决此事,KEY选择是一个能串联业务的参数,比如订单ID。 |
有些场景下子线程无法知道串联上下文的id是什么,更何况是不太想关注增强的代码业务逻辑
…________________________________
From: 李夏驰 ***@***.***>
Sent: Thursday, February 9, 2023 3:14 PM
To: alibaba/jvm-sandbox ***@***.***>
Cc: lossend ***@***.***>; Author ***@***.***>
Subject: Re: [alibaba/jvm-sandbox] 请问sandbox可以支持用户自定添加transformer吗 (Issue #411)
线程间上下文传递和AOP无关,主要出现是一些代码调用联跟踪的场景,不支持的原因还是想尽量保证sandbox功能的纯粹。我们实际写的时候的确会有遇到类似的问题,我的常规处理做法是用一个全局的WeakMap来解决此事,KEY选择是一个能串联业务的参数,比如订单ID。
―
Reply to this email directly, view it on GitHub<#411 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AL34E4L4ZWHEMRYH66L524DWWUCWZANCNFSM6AAAAAAUWCYL7I>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
我考虑下,直接支持掉内部线程的场景。思路也是有的 |
当前我调研的结果是要支持多线程最少冲突的解决方案是把threadlocal以field的方式插入到runable或者callable对象中,直接用ttll包装类可能存在类型转换或者不支持forkjoin的场景
…________________________________
From: 李夏驰 ***@***.***>
Sent: Saturday, March 11, 2023 7:08 AM
To: alibaba/jvm-sandbox ***@***.***>
Cc: lossend ***@***.***>; Author ***@***.***>
Subject: Re: [alibaba/jvm-sandbox] 请问sandbox可以支持用户自定添加transformer吗 (Issue #411)
我考虑下,直接支持掉内部线程的场景。思路也是有的
―
Reply to this email directly, view it on GitHub<#411 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AL34E4LJB3N5VGR6MLD7YM3W3QQF7ANCNFSM6AAAAAAUWCYL7I>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
No description provided.
The text was updated successfully, but these errors were encountered: