jacker wrote on Mar 23
rd, 2011 at 2:57pm:
Perhaps I should have asked this question first...
The Scenario: My application is a candidate database for a job placement business. They have seven offices, two Sesame servers, and four different but almost identical Sesame applications. Some users connect to Sesame over the Internet, but the servers are dedicated to running Sesame and are NOT configured as web or ftp servers (and I don't want them to be, either).
Is there a particular reason not to run an FTP server? Is this a publicly available (on the internet) Windows box?
Quote:My goal is to allow the user to upload and "attach" candidate resumes (Word or PDF) to a candidate record in the Sesame application. I assumed I would have to use a separate ftp server as a storage location for the resumes, hence my recent questions.
A separate bit of software, or a different computer?
Quote:However, is there a communication method/protocol in the API for up- and downloading documents to the Sesame server *without* using FTP or HTTP? It would need to work over the Internet since some clients are remote (so Windows networking is not an option, unless I entertain a tunnel or something like that).
Perhaps the better method is to use Windows to expand the private network to include the remote users thereby bypassing the entire FTP method/problem, and use regular ol' File I/O instead?
This must be a fairly common problem...
Not a very common problem in that most people don't rule out using FTP or HTTP. Using Windows networking or even a Windows based server through an open internet connection is cumbersome and dangerous. Sharing files using Windows networking through a non-encrypted connection is likely to be very dangerous.
I would recommend running an FTP server on the same computer that is running the Sesame server. If that is impossible, you can encode the .doc and .pdf files using base64 encoding and embed them in a hidden linked element on the form. Then, on retrieval, provide a button that decodes them. You could also use the SBasic networking commands and a server side mass update to send the files.
Sesame3 has internal file transfer, but because server security is important, and we have had very little demand for it, it was never implemented in Sesame2.