A Design Question.
-
I wrote a class that i can essential use any where for any of my Inet enabled applications. It serialize's/compresses/encrypts objects and sends them over a net work were it will rebuild it and return the object. it works great but my problem is, i am writing a Chat/File sharing application..it works fine...but i love to criticize my own code and think of how i can make it more efficient, but my lack of experience in developing internet applications and data packets to send is really leaving me stumped. Could anyone help me and point me in the write direction ? i want the system to be as Secure as possible despite the fact that the objects are already encrypt. Anyways thanks for baring with me here... Jesse M The Code Project Is Your Friend...
-
I wrote a class that i can essential use any where for any of my Inet enabled applications. It serialize's/compresses/encrypts objects and sends them over a net work were it will rebuild it and return the object. it works great but my problem is, i am writing a Chat/File sharing application..it works fine...but i love to criticize my own code and think of how i can make it more efficient, but my lack of experience in developing internet applications and data packets to send is really leaving me stumped. Could anyone help me and point me in the write direction ? i want the system to be as Secure as possible despite the fact that the objects are already encrypt. Anyways thanks for baring with me here... Jesse M The Code Project Is Your Friend...
-
If it Serializes, Compresses, Encrypts and Sends an Object over a network... then it should be 4 different classes :)
it is,..encryption / compression namespaces/classes (rsa,tdes,rc2) and a listener class and a recieving class. I just dont know what type of object to send. I want my program to be secure as in...the use is notifyed that someone wants to send a list of there files, I want the other user (requester) to recieve a encryption key that only they can use to encrypt those files. i have that working and all but i was wondering if there were any examples anywhere on how other people accomplish such a thing ? Jesse M The Code Project Is Your Friend...
-
I wrote a class that i can essential use any where for any of my Inet enabled applications. It serialize's/compresses/encrypts objects and sends them over a net work were it will rebuild it and return the object. it works great but my problem is, i am writing a Chat/File sharing application..it works fine...but i love to criticize my own code and think of how i can make it more efficient, but my lack of experience in developing internet applications and data packets to send is really leaving me stumped. Could anyone help me and point me in the write direction ? i want the system to be as Secure as possible despite the fact that the objects are already encrypt. Anyways thanks for baring with me here... Jesse M The Code Project Is Your Friend...
Do you mind if I ask why you aren't using .NET Remoting?
When I can talk about 64 bit processors and attract girls with my computer not my car, I'll come out of the closet. Until that time...I'm like "What's the ENTER key?" -Hockey on being a geek
-
Do you mind if I ask why you aren't using .NET Remoting?
When I can talk about 64 bit processors and attract girls with my computer not my car, I'll come out of the closet. Until that time...I'm like "What's the ENTER key?" -Hockey on being a geek
Well i found from school that using .net remoting can do the samething but i want the raw power of sockets. knowing who is connect when/where/there IP, i assume you can write this into all of your objects and do the same with remoting, but why re-invent the wheel ? and for some reason even though i spent alot of time with remoting in school i seem to beable to use Asyncronous Sockets alot easier, they just make sense to me. And i have alot of power on how i recieve the objects, for example..in my recieving callback i have a stream write the recieved bytes to a file so it doesnt hog up my memory while it waits to download all of the object. This saved alot of memory because sending files encapslated in a class are very large, my socket recieves every connection and give it a unique output and saves the reieved bytes to that output. The unqiue output dir is saved in my state object in my recieve callback and i just reuse that same state object the next time around. Once the object is fully downloaded i move on and decrypt the saved bytes, decompress / reserialize, and the other user recieved it fine. Deep down inside the remoting calls uses sockets as well...although the remoting classes are more user friendly and by all means not dumbed down at all. (it also generates the sockets for you on the fly...which is awesome) Jesse M. The Code Project Is Your Friend...