>>I am working on an application where I need to send via FTP or WebService a record with about 10 or 12 columns approximately every 2 minutes. I feel there is a need to queue these uploads since the network may not be always available.
>>
>>I have an application thread that will create the record and needs to store it somewhere for upload.
>>I have another thread that I want to monitor for new records and attempt to upload them in a LIFO manner.
>>I have a web service and FTP site that will receive the records and store them in a SQL database.
>>
>>My questions are:
>>What is the best method to store/ queue the records ready to be sent off?
>>What is the best object type to send them as where they can be received by a web service or ftp?
>>
>>I know this is a little wide open question, but I am in the early stage of figureing out how to best do this. I ultimately want all my upload data to go via the web service so I can secure it without needing to pass out FTP credentials. I was thinking about using the web service to retreive the FTP credentials and then the app would use them to FTP the file but that would limit the type of object I can send up to a file (maybe xml).
>
>I would consider using Web Service to transfer the content within a XML approach. This is how we do it.

Hi Michel,

To expand then: I could use a serializable entity object to create the record and serialize it into a local folder. Then I could have a DataManager class to monitor the folder and upload the xml file to the web service. This should be pretty light weight I think. Do you use security on your web service? I was thinking of a method that had two extra parameters for a userid and a password. If they weren't both passed in correct I would just ignore the request. I am not too familar with web service security.

Tim