简体   繁体   English

通过本地或远程netLDI访问Gemstone / S服务器

[英]Accessing a Gemstone/S server via a local or remote netLDI

Gemstone/S is generally accessed via netLDI service. Gemstone / S通常通过netLDI服务访问。 I have a Gemstone/S on a hosted server and I connect to it from my development environment in my notebook. 我在托管服务器上有一个Gemstone / S,我从笔记本中的开发环境连接到它。

The question is, what is best practice (or provide for a more stable environment): connecting to a local netLDI service and having it deal with a remote Gemstone/S, or connecting remotely to the netLDI running alonside the Gemstone/S server? 问题是,什么是最佳实践(或提供更稳定的环境):连接到本地netLDI服务并让它处理远程Gemstone / S,或远程连接到运行Gemstone / S服务器的netLDI?

I'm currently using the second option (as above) to connect via SSH port forward from a tODE/Pharo setup in my notebook to the netLDI service running on my hosted server. 我目前正在使用第二个选项(如上所述)通过SSH端口从我的笔记本中的tODE / Pharo设置连接到我的托管服务器上运行的netLDI服务。

AFAIK, Dale developed tODE to be used exactly in the way (2nd option) you described. AFAIK,Dale开发的tODE完全用于您描述的方式(第二选项)。 His earlier solution used a chatty protocol from a Pharo image to connect to the netLDI. 他早期的解决方案使用Pharo图像中的繁琐协议连接到netLDI。 That worked best running the pharo image on the same machine as the Gemstone, and connecting through VNC (preferably compressed, or NX). 最好的方法是在与Gemstone相同的机器上运行pharo图像,并通过VNC(最好是压缩的,或NX)连接。 That was perfectly all right with a server on the same side of the continent (latency 40ms) but not so nice connecting from Europe to a US server. 对于大陆同一侧的服务器(延迟40ms)而言,这完全没问题,但从欧洲到美国服务器的连接并不是那么好。 tODE deals much better with long latencies. tODE在长时间延迟方面处理得更好。

I don't know, but would expect the netLDI to need to be closer to the stones than the clients. 我不知道,但预计netLDI需要比客户更接近石头。

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

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