The best connection

The use of specific JADE features and proposals for new feature suggestions
ConvertFromOldNGs
Posts: 5321
Joined: Wed Aug 05, 2009 5:19 pm

The best connection

Postby ConvertFromOldNGs » Fri Aug 07, 2009 10:45 am

by JADE Kid - Ray Hidayat >> Sun, 3 Dec 2000 23:26:52 GMT

I was just wondering... whats is the fastest way to send data from one computer to another using Jade.

Is it TCP/IP, where you all have your own program installed on your computer and connect up to the server, send the data, and then disconnect.
- or -
Is it thin client, where everyone uses the thin client to connect up and uses the database and notifications to send data around? This also includes the time taken for all the processing that is done on the server to get back to the thin client.

Also, which is better?

--
Ray Hidayat
JADE Kid - 2000
www.jadekids.com

ConvertFromOldNGs
Posts: 5321
Joined: Wed Aug 05, 2009 5:19 pm

Re: The best connection

Postby ConvertFromOldNGs » Fri Aug 07, 2009 10:45 am

by Krull >> Tue, 5 Dec 2000 5:03:22 GMT

Ray,

It might make it easier for someone to answer this question if you explain what you are trying to achieve.

Each thin-client program (jade.exe) uses TCP/IP to communicate with its application server. If you deploy one or more application server nodes in multi-user mode, then they will also use TCP/IP to communicate with a database server in the same fashion as a jade.exe deployed as a standard (or fat) client. The decision whether to deploy thin-clients, standard client or a combination of both is usually based on several factors including but not limited to the geographical location of the end-users, the type and speed of the network connectivity they have to the processing center (hosting db server and app server(s)) and security requirements.
I was just wondering... whats is the fastest way to send data from one computer to another using Jade.

Is it TCP/IP, where you all have your own program installed on your computer and connect up to the server, send the data, and then disconnect.
- or -
Is it thin client, where everyone uses the thin client to connect up and uses the database and notifications to send data around? This also includes the time taken for all the processing that is done on the server to get back to the thin client.
Also, which is better?

Better at what?


Return to “Feature Discussions”

Who is online

Users browsing this forum: No registered users and 0 guests

cron