vfs-devel

Re: [Vfs-devel] First on the topic list?

[Abdul-Wahid P. <ee...@we...>]

 

> Save the uploaded file as 'VFS$file_id'
> When the user goes to download the file copy the stored file over to the
> original file name or create a sym link to the stored file. What's your
> ideas? Copy or symbolic link? or does it really matter?

I think that we should have an option in the config.inc file to allow them to
use mod_rewrite where it is available. mod-rewrite does an excellent job and
is so easy to set-up. Look at the .htaccess file in the distro. Otherwise,
probably a symlink would be quicker to set-up especially for large files that
are over say 20 Mbytes. 
 
> 
> I've checked out the class. Looks to be very clean. Also looks like it will
> get the job done.

If we are going to move to class.DBI, which I think we probably should. Then
we need to finalise which files are going to do what and then port the SQL to
use class.DBI This is what I am thinking of as a structure:


1. Every page - has a call to header.inc at the top

2. header.inc - has a few functions that are used througout the site and a
call to vfs_auth.inc and db_wrapper.inc. It also loads the config.inc file and
sets up the configuration variables.

3. db_wrapper.inc - provides and sets up the generic database functionality
and loads either some_database.DBD or some_database_wrapper.inc


BTW Tony, have you setup your CVS access to the code? You should be able to
make changes using your s/f login id directly to the CVS


Regrads,

AW

Re: [Vfs-devel] First on the topic list?

[Tony K. <tk...@ca...>]

All sounds good to me. As far as the CVS account, not yet. I'll do that
tonight.

Tony Kirk

----- Original Message -----
From: "Abdul-Wahid Paterson" <ee...@we...>
To: <vfs...@li...>
Sent: Monday, June 05, 2000 7:36 PM
Subject: Re: [Vfs-devel] First on the topic list?


>
>
> > Save the uploaded file as 'VFS$file_id'
> > When the user goes to download the file copy the stored file over to the
> > original file name or create a sym link to the stored file. What's your
> > ideas? Copy or symbolic link? or does it really matter?
>
> I think that we should have an option in the config.inc file to allow them
to
> use mod_rewrite where it is available. mod-rewrite does an excellent job
and
> is so easy to set-up. Look at the .htaccess file in the distro. Otherwise,
> probably a symlink would be quicker to set-up especially for large files
that
> are over say 20 Mbytes.
>
> >
> > I've checked out the class. Looks to be very clean. Also looks like it
will
> > get the job done.
>
> If we are going to move to class.DBI, which I think we probably should.
Then
> we need to finalise which files are going to do what and then port the SQL
to
> use class.DBI This is what I am thinking of as a structure:
>
>
> 1. Every page - has a call to header.inc at the top
>
> 2. header.inc - has a few functions that are used througout the site and a
> call to vfs_auth.inc and db_wrapper.inc. It also loads the config.inc file
and
> sets up the configuration variables.
>
> 3. db_wrapper.inc - provides and sets up the generic database
functionality
> and loads either some_database.DBD or some_database_wrapper.inc
>
>
> BTW Tony, have you setup your CVS access to the code? You should be able
to
> make changes using your s/f login id directly to the CVS
>
>
> Regrads,
>
> AW
>
>
>
> _______________________________________________
> Vfs-devel mailing list
> Vfs...@li...
> http://lists.sourceforge.net/mailman/listinfo/vfs-devel
>