>>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.
>
>If you use WS, just go via HTTPS. If you are really concerned, use client side certificates or added tokens sent especially from server to known receivers. Login can also be split from the actual WS and logininfo then forwarded cookie-like into the header of the WS (similar to something java/AXXIS uses). The WSDL is housed then on another URL only reachable to authenticated users (warning: SOAP toolkit is likely to barf on such strategies <g>).
>
>For FTP use FTPS, FTP over SSH. The time frame of 2 minutes should be workable - I used similar setups on government services as a client. WinSCP gets you started<g>.
>

I can't contend that I know how to do all that, but I did understand the concept. When I said 2 minutes however I was referring to a single pc running the application. The web service may have to field incoming from say 24 pcs all sending on the approximate 2 minute interval. When you said 2 minutes should be workable, were you saying it would be better if the time was shorter or longer?

Tim