Sybase 客户端/服务器设置
在我工作的地方，客户端程序实际上是位于内网的一个exe文件的快捷方式。所有用户实际上都使用相同的 exe 文件。
这是设置客户端/服务器环境的正确方法吗？ 这会导致 CPU 使用率高吗？
我始终认为每个用户的PC上都应该安装客户端程序。 但该程序需要一个.ini 文件，每个人都可以轻松查看内容。 （数据库用户名、密码等） 如果我要在每台电脑上安装该程序，安全的方法是什么？
我们总是会遇到诸如程序挂起、连接速度慢等问题。 您认为我们设置环境的方式是原因吗？
At the place where i work, the client program is actually a shortcut for one exe file locate in the intranet. All the users practically using the same exe file.
Is this the correct way of setup an client/server environment?
Does this results in high CPU usage?
I always believe that client program should be installed in every user's PC.
But the program need an .ini file which everyone can easily see the content. (database username, password, etc.)
What is the safe way if I were to install the program in every PC.
We always have problems such as the program hangs, slow connection, etc.
Do you think the way we setup the environment is the cause?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
网络安装并不是全局“不正确”的，尽管正如您所指出的，当您的网络基础设施不太可靠时，它可能会导致问题。 PowerBuilder 也有一些错误（在特定版本中，您没有提到您的错误），这些错误仅在可执行文件位于网络资源上时表现出来或更为明显。我不确定网络安装是否是我的第一个建议，但我不愿意称其为“错误”。
当您不进行网络部署时，访问全球信息是一项挑战。我开发过的大多数应用程序要么在安装时部署此信息，要么通过数据库共享它。 （不过，从来没有一个应用程序共享用户名和密码...颤抖...我想可能有一些情况。）在安装时部署到本地文件假设信息是非易失性的（或者至少更新频率不高于发布版本），或者信息将定期与网络可访问位置同步。您可以使用多种实用程序来同步这些资源，也可以在应用程序中对其进行编码。
至于将问题归咎于网络安装，我们没有足够的信息来安全地做到这一点。 （可以肯定地说，本地安装可能会出现挂起和“连接速度慢”的情况。）您必须自己进行跑腿工作才能获得这方面的证据。
祝你好运，
特里
A network installation is not globally "incorrect", although it can, as you point out, cause problems when you have a less-than-reliable network infrastructure. PowerBuilder has also had some bugs (in specific versions, you don't mention yours) that only manifest themselves or are more pronounced when executables are on a network resource. I'm not sure a network installation would be my first recommendation, but I'd hesitate to call it "wrong."
Access to global information is a challenge when you don't network deploy. Most apps I've worked on either deployed this information on installation, or shared it through the database. (Never had an app that shared user name and password, though... shudder... I suppose there may be some cases.) Deploying on installation to local files either assumes the information is non-volatile (or at least not more often updated than releases) or that the information will be synced with a network accessible location on a regular basis. There are several utilities you can use to sync these resources, or you can code it in your app.
As for pinning your problems on network installation, we don't have enough information to safely do that. (It's safe to say that hangs and "slow connections" can occur with local installations.) You'll have to do the legwork yourself to get evidence to that end.
Good luck,
Terry