Content Management System

J2be info at
Wed Mar 29 13:19:29 CEST 2006

> Me: You can have a file-system on a common network server. I can even
> have a network server and give remote access to people over a VPN. I
> can host content on a terminal server, I can give them VNC clients, or
> an RDP client, and let them browse what they want to.
No, because the contents are published in a different manner.
Think about a "Shop" and a "deposit area", they have the same 
but at the same time they are exposed in different manners.
In the shop you can walk in and be comfortable by watching all the exposed 
in the deposit area.

> Myself: How will they know "where" to find what?
> Me: Come again?
Searching or by following the suggested links.

> Myself: With all those avenues you mentioned, you won't publish
> content. There will not be a taxonomy. You will just be dumping files
> on another remote server. How will the users "find" what they want?
It's not a *dumping* files but publishing contents.

> So, is a CMS all about:
> 1. Taxonomy
> 2. Publishing content in a Web based format
> Me: What about binary objects that cannot be published in HTML?
3. Other things.
Binary contents can be linked for download.

> Myself: Yeah! What about them, dude? Use your head. What about them?
> Heard of a hyperlink? Heard of HTTP? FTP? No?
> Me: OK. I get it. But...I *still* don't get it, man. Why did we need
> this? More importantly, where are the boundaries? I believe CMS also
> lets users edit and publish content on-the-fly.
The boundaries are the different methods.

> So, again, where are the boundaries? What about non-public content?
> What about access rights? Do you have seperate users on CMS's having
> their seperate folders as well, where they could put their own private
> content? Or, is the idea behind CMS about "sharing" and so they put
> only that which they need to share and not the private stuff.
> Do CMS's also allow access rights or authorization levels *per*
> resource/file/unit of content that is uploaded on to them? Or, are they
> role-based - e.g all users of this group will be able to access all
> files, and users of that group will have read-only access to this
> website.
The CMS can be created with any kind of feature, with restrictions or not to 
That's up to the person to know what they want to do with the CMS.
It could be open to anybody or restricted.

CMS is only a generic acronym.


Leonardo Armando Iarrusso - J2Be
www: - e-mail: info[at] 

More information about the Python-list mailing list