|
Marco,y
Do I understand correctly that users are connecting from an RDP client to
an RDP server? That the RDP server is running browser instances for each
remote user? If so, why would you do that?
Wouldn't it make more sense for browser clients to connect directly to an
HTTP server? I can't think of any reason for putting an RDP server in the
middle. I'm curious about what use-case you may have had in mind?
My thinking is that web interfaces and RDP interfaces compete against one
another, architecturally. Yet it appears that you thought that they might
be complementary.
It also seems intuitive to me that an RDP interface in the middle would be
extremely resource intensive and prone to poor performance - like what
you're reporting.
Nathan.
On Sun, Apr 5, 2020 at 4:11 AM Marco Facchinetti <
marco.facchinetti@xxxxxxxxx> wrote:
Hi, since we rewrote our main IBM i ERP package to be Web based we also took the chance to use it on a Power only machine, no others servers in between. Our plan was to execute our ERP in a RDP like virtualized desktop hosted on a Linux platform (Power). The main reason we choose this way is because communication exchange between the browser and the backend is heavy. The LAN Linux and IBM i use to communicate with each other is virtualized so none of the OS's even reach the switch, of course Linux reach it as it has also to communicate with users, but internal communications are 100% virtualized and I have to say that run really fast. Now our problem is that we sat up various environments: - Red Hat V8 - Red Hat 7.3 - Ubuntu 16.x - Ubuntu 18.x using various desktop virtualization (Dockers, VNC, Xrdp, X2Go and others) but all of them got performance problems when executing the client part of our ERP (Javascript) in a browser. If I execute it using the same Browser (typicall
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.