Hello,
When you use my Parallel archiver
as a database server or a hashtable database server from the
hardisk, it will have a O(1) complexity and fast access on all
the following methods:
DeleteFiles() , ExtractFiles() , Extract() , GetInfo() , AddFiles() , Test() , so Parallel
archiver is extremely fast with this O(1) complexity, faster than a database like MySQL or SQLLite that have a complexity of log(n) i think.
So as i said to be able to use my Parallel
archiver as a database or hashtable from the hardisk, no need for you to use a TCP/IP client-server
mechanism between the local process (that
you will start on your server for each client) and Parallel archiver, but
you have to use a TCP/IP client-server mechanism between the local process that
you will start on your server and the remote process of your. And you have to compress your files as archives
(to serve the files as compressed archives to be able to lower the load on your
server and to boost the response time of your server) and store them in your archive , after that you have to use the Distributed Reader-Writer Mutex that i wrote(you will find it on my website) inside your application to protect the write access to your archive etc., that's all.
Thank you,
Amine Moulay Ramdane.