General > Off Topic
New IM idea
Shasta:
Hey sorry I didn't reply sooner, I've been pretty busy this quarter.
I've actually got 90% of a working solution using a socket server for IM sitting around somewhere. I keep ending up with time to program stuff when I'm on machines that I don't have the actual code base :wacko:
Botsareus:
Expending more on the scalability issue, I was thinking of making a socket based P2P system, I'll have a new flow chart by Friday...
Botsareus:
K, got it done today.
This is a decentralized version of what I proposed before, outbound client runs every 500 milliseconds:
One of the obstacles I am having is: How to tell if "client is busy"? (Or, from the old chart, "Server is Choking")
(Shasta, I hope this is what you had in mind)
ikke:
There is enough P2P code out there to show the way. Or to use perhaps.
Botsareus:
I know, I am looking at what Shasta has done first...
This is a little different from ordinary P2P code. Let me explain:
1.) The inbound client does NOT know the size of the file being transferred to it.
2.) The inbound client can be busy with a current transfer, but, it must automatically except any transfers
I am confident it can be done after doing some research. Still, the R&D is a little heavy and I tend to procrastinate when I have too much R&D. :wacko: Here is the extent of my system.net.sockets experience if any one has vb2k10 and wants to take a look. If you just have .net framework 4.0 you can take a look too. Had down to the bin/debug/ folders and run server and client exe files. The only update I did to the server side for a school project was remove a client from server when server receives an 'exit' command:
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version