 |
|
|
Peer-to-Peer (P2P) Support
Technote: Q00012
Last Reviewed:
June 6, 2002
The information in this article applies to:
e/pop Professional and Basic (client software products)
e/pop software evaluators considering P2P configurations
Summary
e/pop v3.0 supports both client/server and peer-to-peer (P2P) installations. This tech note describes support for P2P installations, describing the circumstances where P2P may come in handy.
For best results, WiredRed recommends client/server, but the special circumstances described below may be appropriate for P2P.
Please note that e/pop, in client/server mode, doesn't necessarily require a dedicated server machine. Contact WiredRed for more details.
P2P versus Client/Server is cost neutral. This choice makes no difference in price.
e/pop Legacy Includes Largest P2P Installations
WiredRed is currently shipping e/pop version 3.0. This version of e/pop is capable of supporting both P2P and client/server configurations. Many long-time WiredRed customers may recognize that the early versions of e/pop supported some of the largest peer-to-peer messaging and real-time communications installations in the world – with several telecommunications and utility companies supporting 1000's of users.
WiredRed will continue to support these P2P environments. However, many of these larger installations have already moved to a client/server configuration because of the advantages further described below.
Definitions & Key Considerations
P2P. As used here, P2P refers to installations of e/pop without the e/pop Standard or Enterprise Server. Workstations communicate with each other directly over a local area network (LAN).
Client/Server
As used here, Client/Server refers to installations with e/pop Standard or Enterprise Server. Workstations communicate with a designated e/pop Server, which then intelligently routes communications (packets) to other workstations and/or other e/pop Servers.
Dedicated v. Non-Dedicated Servers
The term "server" does not necessarily mean a traditional dedicated machine in the server closet. The "server" can be any machine, Windows 95 or later. Note: Windows NT, NT Workstation, 2000 and XP recommended (i.e., 32 bit versions of Windows). For best results, the Server should be a machine with a "static" IP address (contact Support at WiredRed for alternatives).
P2P – When & Why?
After 3,000 customers installations, WiredRed sees two general exceptions to the ‘always go client/server' rule. The exceptions are:
- Small office LAN, with less than 10 users, where no file server exists or e/pop is a secondary communication channel (no guarantee of message delivery needed)
- Call Centers, under tightly controlled, lock-down environments where network savvy staff can configure e/pop clients to really take advantage of IPX, UDP and multicasting. Other enterprise considerations don't apply.
P2P Advantages
Does not require server or expertise required to install and administer server. Under very narrow circumstances, there are performance advantages with P2P broadcasting (as mentioned in "Call Centers" above).
P2P Disadvantages.
- P2P does not support off-line message queuing (off-line users get their messages when they log back on), private routing (support for WAN, VPNs, firewalls, proxies, & NATs), centrally managed security policies, directory service integration, and all the other enterprise capabilities available via the e/pop Server. These are serious limitations as even small offices have remote users and are starting to take advantage of firewalls, WANs and VPNs.
- It can often be difficult for non-technical staff to distinguish between single v. multiple LAN segments. Customers that seek to avoid technical issues by avoiding the "server," often find more technical issues attempting to communicate over multiple LAN segments. Note that multiple LAN segments can make reliable P2P communications impossible.
- Without a server, there is no guarantee of message delivery. Under P2P, clients place messages on the net, and other clients must be online to "capture" the message. Client/server offers confirmed, audit-capable message delivery. See also Audit & Reporting below.
- Finally, without a central server involved, licensing can be difficult (i.e., under P2P, the license file must be copied to each e/pop user, versus just once to the server).
Cost Neutral!
WiredRed pricing is the same regardless of configuration, P2P or Client/Server.
Audit & Reporting
The e/pop Audit & Reporting Server requires client/server. Audit and reporting capabilities are required in many regulated industries.
Additional Related Material
For additional details, please see Page 1-6 in the Admin Guide.
In some circumstances, "shared installations" (e/pop executables installed on a fileserver v. local disk) can alleviate the licensing issues related to P2P installations. This is an advanced topic, please contact WiredRed for assistance.
Contact WiredRed
In most installations, client/server is the preferred configuration. If your scenario meets one of the special situations described above, and/or if you have any specific questions regarding e/pop in your environment, please contact WiredRed.
|
|
|
