Teamsite Vs FTP Server

Teamsite Version: 6.5

Problem Summary:

The files hosted on one of our FTP servers are very large in size. I need to know the pros and cons of keeping those files in the Teamsite content store rather than the FTP location. As I understand, the virtual file system is only for proper presentation and easy access of content to users and has no intervention in the actual storage pattern in which all content is stored in an encrypted form(Plz correct me if I am wrong) in the IWStore. Now, I need to know:

i. Is there any limit to the size of files that can be stored in Teamsite?
ii. As I understand, the files would have to be decrypted by Teamsite before they would be downloaded. So, can storing large files on Teamsite give rise to any performance issues in downloading those files?(I am not aware of the working in FTP)
iii. Is HTTP based file downloading advantageous or disadvantageous compared to FTP based file downloading and in what regard?

Hope I have given you a fair idea of the problem's nature. I am trying to evaluate Teamsite wrt FTP Server for storing files. Also, please do correct me if I have wrongly understood/stated something above.

Find more posts tagged with

Comments

RonaldV

Samir,

your question is somewhat confusing. Just to explain the concepts of teamsite for you:

Teamsite is a "content management system". That is a tool to manage (e.g. edit, archive, version, authorise, well manage) your content.

FTP is used as a "file server system", that is to share, up- and download files.

That is, Teamsite should NOT be used as a ftp-server. Period. [Well unless you accept the limitations of that scenario, there is too many to explain here]

The normal scenario would be to "manage" your files in teamsite, deploy them to your ftp (or http) file server where end users can access them.

Now, what was you question again?

Samir_Friend

Samir,

your question is somewhat confusing. Just to explain the concepts of teamsite for you:

Teamsite is a "content management system". That is a tool to manage (e.g. edit, archive, version, authorise, well manage) your content.

FTP is used as a "file server system", that is to share, up- and download files.

That is, Teamsite should NOT be used as a ftp-server. Period. [Well unless you accept the limitations of that scenario, there is too many to explain here]

The normal scenario would be to "manage" your files in teamsite, deploy them to your ftp (or http) file server where end users can access them.

Now, what was you question again?

Hi Ronald,

My reference is just to the storing, versioning etc. of static files which are very large in size. If I upload them to the Teamsite content store and then download them through the end site, what issues may arise in comparison to the working of an FTP Server. Basically, I am looking out for answers to the following specific questions:

1. Is there any limit to the file size that could be stored in Teamsite?
2. What would be the limitations(as you mentioned) of using Teamsite to store large files instead of an FTP Server?
3. What overheads, performance and access issues could I encounter when using Teamsite to store large files which would be downloaded by the site user?

Hope you get my point now.......