From: Hector Santos on 9 Feb 2010 06:12
This is a classic RPC C/S solution. Keep all file storage/location
information on the server side only. Clients know nothing. Classic
definition of Client/Server.
Use true RPC or COM+/DCOM.
Eddie Paz wrote:
> I had a similar situation and I opted to store the files in the database
> itself (image field). The files were small and not too many (thousands
> of large files is not recommended to put in the database). This solution
> was the best as I could get to the files from all my three Linux, MFC,
> and IIS applications; plus, I also added a fairly simple caching to the
> The UNC option was my alternative solution had it not been for Linux and
> the need for Samba and that whole mess.
> "Bogdan" <bogdan(a)nocompany.com> wrote in message
>> I have an app that needs to run in a client-server environment. That
>> is, the app (MFC native) is installed on multiple workstations and
>> accesses a database on a 'server'. The app stores media file paths
>> (video, audio, images, etc.) in the database. These files need to be
>> played on any workstation running the app as well as on the server.
>> In addition, I also have a Web app (asp.net 3.5) that needs to access
>> the media files and display them in a Web page.
>> The app was initially designed to work on a single computer. I need
>> to make some changes so it could function in a client-server
>> scenario. One of the issues I need to deal with is file paths that
>> are stored in a sql database.
>> I'm looking for some advice on what format would be most appropriate
>> in this case. I was considering an 'old' way of mapping network
>> drives to folders. For example, I could make sure that each
>> workstation as well as the server have M: drive mapped into a folder
>> on the server where the files are stored. This would work without any
>> code changes. Unfortunately IIS has some issues with network drives
>> so I need to look for other solution.
>> Another option would be to use UNC paths. This would require quite a
>> bit of work - _makepath(), _splitpath(), translation of paths to UNC
>> in cases where file path is passed from drag-and-drop, standard
>> dialogs, etc.
>> Has anyone gone through a similar excursive? Any advice?
Prev: Saving as PDF?
Next: Loading MBCS extension dll into Unicode regular dll