>>>Well, you could create an application that runs on the FTP port and
>>>dynamically generates content in response to FTP commands. :-) It
would
>>>probably be easier to create or integrate a WYSIWYG editor that does
what
>>>you want in the first place!
I have done this. It works very well. I had to obtain/create a full
blown FTP server.
I added direct SQL Server 2000 Support.
I created an ASP (Web) based to view the FTP tree as Assets or documents
in the CMS. But I hate uploading XMl or HTML as pages...I prefer
storing them in the Database. I tend to be militant about storing
content in the database...and I feel like a broken record.
I created a COM (Active X Control) that allows ASPes to talk to the FTP
server and send them the new special FTP commands.
What do you think?
FTP is a great back-end for CMS...my users upload thousands of
files...one one Law Firm we created a CMs for upload 75 megs of patents!
The FTP told the CMS Core to create links support database entries so
when the upload was complete...the Web site had a navigation.
Issues to consider:
1. Who gets to upload? FTP Permissions have to be tied to a Relational
Database stored procedure check. (See what I mean..I am militant)
2. UNIX Permissions are Legacy and may not work in a CMS context.
Since most CMSes have the concept of WORKFLOW there is more to it that a
set of Octal Numbers. :) So be prepared to spend 6-8 weeks designing a
new permission scheme that replaces UNIX with an abstracted CMS
permission scheme. Oh ya...but then you set have to set octal permission
bits anyway.
3. FTP uploads need to be treated as database transactions and therefore
an entirely new set of operational procedures need to be considered.
Our solution was to create a master "REFRESH" feature that synchronizes
the file-based content with the view on the database.
4. What the hell does DELETE mean? In fact deleting a file using FTP
has HUGE and potentially disastrous implications. What if the file
being deleted is used by other content? Deleting it would create 404's
or worse system failure. So your programmers need to always check if
content exists...or...you need to always check if content is being used
before it can be deleted.
The next version of our CMS FTP server talks XML...
Tony
www.pillarsoftware.com
--
Mark Thomas |_|
Internet Systems Architect -+-
User Technology Associates, Inc. |
[EMAIL PROTECTED] /-\
--
http://cms-list.org/
more signal, less noise.
--
http://cms-list.org/
more signal, less noise.
