Thanks Paul for your reply. I have checked out the Attachment class and see how it works. However, this allows me to attach a file and send it to the server, or the server send it to the client(download or upload from server). What I am wanting to do is have client A see the files from client B and upload or download files from it. The webservice would still be the middle man I guess, but I don't want it to stop at the webservice, rather pass through it.
I have the code for the webservice. I wonder if I can create a listener channel on each client using that code and instead of going through the webservice at all I can pass it to the each client. I already have a IIS object that holds logged in clients information (username, IP, machinename). Forgive me while I brainstorm..I don't think the client would mind if while installing the software a webservice gets installed as well. Instead of a listener class it would be the actual webservice. I wonder what the implications would be if I installed the webservice for this on each client? My IIS Object can also hold the uri for each clients webservice and it can be used when file transfer was to take place. What are your opinions? Good, bad, ugly. Anything will do. Thanks again for the reply. Steve -----Original Message----- From: Unmoderated discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED] On Behalf Of Paul van Brenk Sent: Monday, June 20, 2005 4:02 AM To: [email protected] Subject: Re: [ADVANCED-DOTNET] Anyone have experience using DIME? Checkout the attachement class in MS WSE 2.0 sp2, I've had some experience using it in the 1.0 version. Paul -----Original Message----- From: Unmoderated discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED] On Behalf Of Angela Tocco Sent: Friday, June 17, 2005 15:57 To: [email protected] Subject: [ADVANCED-DOTNET] Anyone have experience using DIME? Good Morning and happy Friday. I was reading an article on the website '15 seconds' about how to create a Document Sharing System using DIME (Direct Internet Message Encapsulation). The article can be found at this address and the code I used is there as well: http://www.15seconds.com/issue/021218.htm The article talks about using Web Services and a client. Basically the client can upload and download files from the server. However, I am curious as to whether I can change this and have it go client to client, rather than client to server. Anyone familiar with DIME to know if I need to use a Web Service or not? I was thinking about creating a class in both my clients applications that would include the code used in the Server application of the DIME Example. Instead of a web service it would be a class. My goal is to add a file transfer plugin to my Tech Support application. The trick is I cant use sockets because the application is using .Net Remoting and it has to be able to go through port 80, outbound only. DIME, Genuine Channels, regular .Net Remoting can do this. Only problem is I need to be able to go client to client. Not sure if DIME does this but with Genuine Channels if you send a packet to a client, ALL clients receive it. There is a fix for this but its rewritting it and I don't have time to do that. If you cant help with DIME, any suggestions on how to upload and download files to a client without a middle man and .Net Remoting? Any help would be appreciated. Have a great day, Steve =================================== This list is hosted by DevelopMentor(r) http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com =================================== This list is hosted by DevelopMentor. http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
