Posted by Jim Guerber on July 06, 2009 at 15:08:46:
I have wished for several years that CometServe could serve files on servers that could not host our software. This would include NAS boxes, SAN devices, Linux boxes etc. These devices have a machine name on the network but can not host our software.
In the past we were able to connect to these devices by using type "N" directories. That is no longer possible.
If the device were configured as a network drive letter, each copy of CFAM would think that the drive was a local drive. This would cause the local copies of CometServe to attempt to access this folder simultaneously, causing all kinds of grief.
The CometServe that serves shared folders is run as a service. Windows services do not have access to network drives.
We have not experimented with running Cometserve as a different user such as administrator, but I don't think that even then, network drives would be accessible.
Here is what I propose:
Lets change CometServe to recognize folder syntax such as //ServerName//NASName/ShareName/Folder. During startup, CometServe would attempt to open //NASName/ShareName/Folder/QDIR.DIR. If successful, that directory would be accessable.
What do you think? Is this feature even needed?
Each file can be a maximum of 1MB in length Uploaded files will be purged from the server on a regular basis.