在2.3 使用 tarscloud/framework 部署框架中

5. 启动框架从节点

如果希望多节点部署, 则在不同机器上执行 docker run ...即可, 注意参数设置!

最新版本:

docker run -d \
    --name=tars-framework-slave \
    --net=tars \
    -e MYSQL_HOST="172.25.0.2" \
    -e MYSQL_ROOT_PASSWORD="123456" \
    -e MYSQL_USER=root \
    -e MYSQL_PORT=3306 \
    -e REBUILD=false \
    -e INET=eth0 \
    -e

非常感谢大家对 SOFAStack 开源的关注和支持，这是我们前进最大的动力。

收集目的

• 了解 SOFAStack 的使用场景以便更好的规划技术路线
• 聆听社区的不同声音，让 SOFAStack 变得更好
• 吸引更多的开源爱好者参与贡献，共同打造 SOFAStack

收集方式

请按如下参考格式回复本 Issue 进行登记：

* 公司/组织名称：蚂蚁金服
* 地点：中国杭州
* 网址：http://www.antfin.com
* 使用组件及场景：全套金融级分布式中间件
* 联系方式：[email protected]

展示

我们会定期同步信息至「Awesome SOFA」的用户列表中。

服务

In our codebase, we push RequestContext and immediately run some code with try-with-resources.
For example:

try (SafeCloseable ignored = ctx.push()) {
    logger.trace(decorate(msg));
}

If RequestContext provides run(Runnable) or call(Callable) we can reduce boilerplate code and simplify it.

ctx.run(() -> logger.trace(decorate(msg));

This is inspired by g

@jonhoo @tikue

• Explain | syntax
• Write more about services and clients and when you might return what errors. Have some examples.
• Make it more clear that service implementations must be Clone/Send/'static
  • Add to the readme
  • Add to the macro documentation if it's not there
• Warn of the dangers of mixing FutureService with SyncClient
  • Namely, if the client runs on

Hi,

by a total chance, I've run into this fragment on main page (http://spyne.io/#auxproc=Sync&s=aux :)

To do additional work after the primary method returns, you can set the aux attribute in another service definition class and implement the same method signature

For a total beginner in spyne/rpc world (that is me) this was quite enlighting in terms of what is happening. Earlier

https://github.com/elpheria/rpc-websockets/blob/2f0f59e181e4b5338b878848a53198bcb199ee6f/src/lib/server.js#L417

In case if client socket closes the connection - 'send' will cause an unhandled rejection, which in some production environments might lead to application crash!

Mentioned problem is relevant to any other socket.send call.

Steps to reproduce:

1. Call some long running rpc tas