Thanks for your offer of support.

I've been able to work through what I need to at this point...  I've had some weird problems, one of the most annoying being that under ending time for an auction, random times appear.  I am also running this on a 64bit system, which is most likely the reason why.  Basically everything referencing time functions (for example, "(time - $^T > $config{'max_searchtime'}) && last; # We are the master of our CPU-Usage") fails...  That will always return false on my system, effectively disabling the listing of auctions under a certain category.  (I've disabled this check until I can further check this out...which is fine anyway, since I will be the only one entering auctions...)

This is perl, v5.6.1 built for sparc64-freebsd is my perl version...
I'm working around whatever needs to be worked around in the manner that gets it done in the least amount of time...because I am time constrained.  I apologize for butchering the code  If you so desire, I will let you have a look at the code when I am finished.

In regards to becoming a codeveloper...  I'm not a perl programmer.  I doubt I have one quarter of the skill you have. I'm just a really really determined person who needs to get some stuff done.  I have more experience with C and PHP than perl...  I think eAuction does have great potential, though.

I like how eAuction consists of one perl file, and a configuration file.   With a lot of time, and little smarts, or a lot of smarts, and a little time, it can be nearly whatever one wants.

Once I have what I need to have done, if I have time before the site needs to go live, I will probably convert it to apache's mod_perl compatable code, so I can have better execution times...  Although BSD is renowned for superior fork() performance

What do you think about the serving speed? (4 concurrent requests per second...)

For session tracking, I am implementing an easy url-based system, where a parameter is added to the URL which contains a server-assigned string which is associated with a corresponding filename (of the session id).  Whenever &ssid=string is seen, string is sanitized, and then searched for in the sessions/ directory, and then if it exists and isnt expired, the 'alias' and 'password' info is loaded into $form{...} and a toggle is set, and the said toggle is used to turn off/on features...  And, for example, every 5% of page loads will result in expired sessions being removed...  (idea taken from pastebin.com's cleanup code[and common sense]) I am still implementing it...  

Anyway, I cant work on it if I'm talking about it.

-poxy