Pierre-Mikael Legris <[EMAIL PROTECTED]> writes:
> *About the file upload
> Technically the file upload would take place in parseargs() which
> does get the multipart/form-data datas.
Yep.
> I'm planing to write the upload file part of mod_dtcl, but as I said
> I'm quite new to C coding and my code will have probably to be
> strongly reviewed.
I have already started hacking.
My plan so far is to have two methods of doing it:
dumping it to a file as it comes in - good for big file uploads
dumping it all to a variable - faster and less of a pain in the ass.
config variables: (you have some good ideas there)
maximum size accepted
directory
> # Features i want to see
> * Connection to databases in a keep_alive way.
This is already doable. I create a script in global init or something
that is something like this:
proc get_db_conn { } {
global db_connection
if { [ is the connection open db_connection ? ] } {
return db_connection
} else {
set db_connection [ open db connection somehow ]
return db_connection
}
}
Every time you call it, it returns a DB connection.
> * Levels of variable
> I would like also a top level variables space. Variables that could
> be read/write by any interpreters. I see the use of this for flags
> that indicate that another interpreter is using a resource. Some
> others top level variables could have a long life support. They
> should be able to survive to a server shutdown, by being dumped into
> a file or a db.
Hrmmm, sounds like what a database gets used for;-) You could use
shared memory... but it kind of sucks. Depends exactly what you
need and why. Do your best to describe it, and we can figure out how
it's best to accomplish it.
Snzzzzzzz,
--
David N. Welton
http://www.prosa.it http://www.prosa.it/developers/davidw/
tel +39.049.8043411 fax +39.049.8043412 cel +39.348.2879508
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
