And I apologize for the format of this past message. I didn't do that.
-----Original Message----- From: Unmoderated discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED] On Behalf Of Steve Welborn Sent: Thursday, June 23, 2005 11:20 AM To: [email protected] Subject: Re: [ADVANCED-DOTNET] Anyone have experience using DIME? Quote from J (BTW, why are messages from "Angela Tocco" signed "Steve"?): Because it was somebody elses email address I had to use at the time. All fixed now, this is me. And you are correct about the two clients not knowing each other. I am using IIS to fix this. I use an Interface approach and reference that on each client. It in turn is used by my IIS Object. This basic .Net Remoting approach isnt the only thing I use, Genuine Channels is another approach I use for sending information from client to client. I would use this for sending files client to client, but there is a huge workaround to allow it to be sent to only one client and not all clients. Genuine Channels BroadcastEngine sends every packet to all clients logged in. With DIME, my approach was to have each client application include a DIME webservice and it can be used for file transfer. However, this wouldn't work because the client would have to have IIS installed and the webservice would need to be on that server. Which wouldn't work. Clients should only have to download and use the Application, nothing more. So my question is null and void. It cant work. I will have to go back to my first approach, which worked, but was slow. My basic .Net Remoting object had 4-6 methods in it: PrepareFileTransfer(string username, bool setactive); bool CheckForFileTransfer(string username); bool CheckForDownload(string username); bool CheckForUpload(string username); and a few others.. Basically the file from ClientA gets uploaded to an ArrayList inside the IIS Object. Once complete it sets TransferComplete to true and ClientB sees this and starts the DownloadFile event where it will download from IIS. It was the long way, but it worked. Was hoping DIME would of fixed this. Anyway, thanks for the reply. I will continue to find a better way to do this. Steve(not Angela) -----Original Message----- From: Unmoderated discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED] On Behalf Of J. Merrill Sent: Thursday, June 23, 2005 10:36 AM To: [email protected] Subject: Re: [ADVANCED-DOTNET] Anyone have experience using DIME? At 09:57 AM 6/17/2005, Angela Tocco wrote (in part) >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. If you have two clients that are each restricted to "outbound only" (regardless of port restrictions), they won't be able to talk to each other -- neither can accept a connection from the other so there's no way to establish a direct connection. That has nothing to do with .Net or DIME or anything; it's just TCP/IP. You need a server to stand in the middle. (How could the two clients learn about each other? If each communicates with the server, then there's a place to hold the list of all clients; without that...) If all you're doing is uploading and downloading files, perhaps you should just use FTP. Good luck. (BTW, why are messages from "Angela Tocco" signed "Steve"?) J. Merrill / Analytical Software Corp =================================== This list is hosted by DevelopMentor. http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com ____________________________________________________ Yahoo! Sports Rekindle the Rivalries. Sign up for Fantasy Football http://football.fantasysports.yahoo.com =================================== This list is hosted by DevelopMentorR http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com ____________________________________________________ Yahoo! Sports Rekindle the Rivalries. Sign up for Fantasy Football http://football.fantasysports.yahoo.com =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
