Home
CCIT
RPM
How does it work?
Content Editors
Admin. Module
Pricing
RPM FAQ's
RPM vs FTP
Show me more!
Company Information
Newsroom
Contact Us
Partners
|
|
RPM vs. FTP, HTTP, and LAN Access
FTP
File Transfer Protocol (FTP) was developed in the early days of the Internet as a means for researchers around the world to transfer files of any type from one computer to another. The protocol encompasses powerful system configuration capabilities and was intended to be used only by those with a thorough understanding of its capabilities and with high-level network access authority.
FTP requires a direct connection between the content provider (client) and the server. Any direct connection that authorizes data to be uploaded to the server creates security concerns.
FTP credentials were never intended to be delegated or widely distributed across an organization nor does the protocol provide suitable means for constraining or monitoring its use.
A PowerPoint graphical animation that illustrates how FTP can be abused and how RPM can successfully address FTP’s inherent weaknesses is available by requesting here. (Windows 95 viewer is included.)
For web page management, the CCIT-based RPM solution is a superior alternative to FTP delivery. RPM can run independently or in conjunction with FTP-based publishing products and thereby enable these products to be safely deployed.
HTTP
Like FTP, HyperText Transfer Protocol (HTTP) also presents a security concern because a direct connection is required between the content provider (client) and the server.
Sometimes called browser-based or forms-based editing, HTTP is an awkward and cumbersome protocol to deploy for purposes of content management. Not only are HTTP-enabled solutions browser dependent, they usually suffer from lack of page format freedoms.
LAN
Local Area Network (LAN) connections don't provide any relief from the above security concerns nor do they provide suitable monitoring or management controls.
Sooner or later, there's bound to be trouble...
For lack of a better way, all of today’s web publishing solutions depend on direct FTP, HTTP, or LAN connections for transferring content revisions from the client desktop to the web server. In the right hands, these approaches can work satisfactorily. However, these connections cannot satisfactorily limit web server access and activity nor can they provide selectable management and monitoring controls. In the wrong hands this invites trouble, which can lead to disastrous results.
Delegate Web page management with peace of mind...
With RPM, simply e-mail updates directly onto Web pages. Use any content editor you like. RPM keeps pages and sites fresh while safely delegating partial or full-page page responsibility to those who actually provide the content. Updates can be made as often as desired, and no interaction with the Webmaster or site manager is needed. There is never a direct connection between the content provider and the server. All activity is monitored live and reported immediately.
Reedy Creek
Technologies, Inc.
284 Reedy Creek Road
Four Oaks, NC 27524
|
Voice:
(919) 934-6869
Fax: (919) 934-1537
info@reedycreek.com |
|
