Difference between revisions of "Connection Profile"
From ADempiere
This Wiki is read-only for reference purposes to avoid broken links.
| Line 23: | Line 23: | ||
* Disadvantages: | * Disadvantages: | ||
** More consumption on server resources | ** More consumption on server resources | ||
| + | ** Current implementation slow in loading large data set | ||
''VPN'' | ''VPN'' | ||
Latest revision as of 23:58, 11 May 2008
LAN
- open direct connections to database (a must)
- open connection to server via jboss 1099+others ports (if available)
- can run with the server down
- run processes locally
- get rows directly from database
- Advantages:
- Maybe the faster on LAN env
- Low consumption on server resources
- Disadvantages:
- unsafe (very unsafe from a hacker POV)
- unkillable (as explained in a recent thread)
WAN
- don't open direct connections to database
- open connections to server via http port (a must)
- just can run with the server up
- run processes on server
- get objects from server (server get rows from database)
- Advantages:
- Safer (still have some holes, but they can be controlled in other ways)
- Killable (if the server goes down, all clients are disconnected)
- Disadvantages:
- More consumption on server resources
- Current implementation slow in loading large data set
VPN
- same as WAN but connecting to server via jboss 1099+others ports (a must)
- faster than WAN as it is using native RMI instead of http tunnelling
Pending todo: secureWAN -> https support
