简体   繁体   English

GWT是否与app-engine的多租户支持兼容

[英]Is GWT compatible with app-engine's multitenancy support

只是寻找确认GWT RPC与app-engine基于名称空间的新多租户支持相匹配。

The two technologies are very compatiable. 这两种技术非常兼容。 I have been using them together for a long time. 我一直在一起使用它们。 In fact there are some syntatic sugar that makes them easy to be used together, such are RPC calls. 事实上,有一些合成糖使它们易于一起使用,例如RPC调用。 Plus now your server and client code are in the same language. 此外,您的服务器和客户端代码使用相同的语言。 Using eclipse and the setup that google developed for eclipse and GWT/AppEngine I have all the code in one project with a client, server and shared code. 使用eclipse和google为eclipse和GWT / AppEngine开发的设置我在一个项目中拥有客户端,服务器和共享代码的所有代码。 The client and Shared code gets compiled with GWT and the server and shared code get compiled for AppEngine. 使用GWT编译客户端和共享代码,并为AppEngine编译服务器和共享代码。

I hope this helps. 我希望这有帮助。 https://developers.google.com/web-toolkit/doc/1.6/tutorial/appengine https://developers.google.com/web-toolkit/doc/1.6/tutorial/appengine

Michael 迈克尔

You can try to use multi-tenancy in your GWT-RPC, but it will not be just configuration. 您可以尝试在GWT-RPC中使用多租户,但这不仅仅是配置。 You can use per-user multi-tenancy setting NameSpace using filter, but do not forget that if you start AsyncTasks from gwt-rpc calls you will not have valid user in tasks requests so you will need to figure out how to choose namespace in tasks. 您可以使用过滤器使用每用户多方租用设置NameSpace,但不要忘记,如果从gwt-rpc调用启动AsyncTasks,您将无法在任务请求中拥有有效用户,因此您需要弄清楚如何在任务中选择命名空间。

As long as your server-side implementations correctly handle the multi-tenancy, you'll be fine. 只要您的服务器端实现正确处理多租户,您就可以了。

There is no additional load to using multi-tenancy with GWT-RPC, but there is additional load using multi-tenancy and you won't be able to avoid that with GWT-RPC. 使用GWT-RPC的多租户没有额外的负载,但是使用多租户会有额外的负载,而使用GWT-RPC则无法避免这种情况。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM