Net Programming

I am trying to write a protocol for distributed computer nets. It is going to be a layer between an application and the net to make programming easier, similar to RMI or CORBA.

What desirable characteristics you think it needs to implement, /prog/riders?

>>1
^* /prog/riders

I don't understand what you're trying to accomplish.

I am pretty sure you are going to HaX mY aNuS!

>>3
I'm thinking about a library based on sockets, what would help the programmer on building fully distributed nets. The main idea is achieving transparent host locating and message passing management. It isn't fully developed yet, hence the question, but this is the core.

>>4
beg pardon?

>>6
Hax my anus?!?!?

>>7
Why would I want to hax your anus?

>>1-8
Go away.

>>9
^* >>1-9,11-

>>1
If you are using a high level language that supports it, proxy objects that represent an object on a foreign machine, where method calls get forwarded across the network and the return value gets sent back transparently.  For extra credit, send exceptions back and re-throw them.  Something to look at might be how objective-c does distributed objects (method signatures are extended so you can pass my copy or by proxy), though its probably simpler always pass method args by copy.

>>11
YES ONE FUCKING COHERENT RESPONSE
Thank you. I was thinking about the object layer and i am thinking to write in plain C or C++ the net management issues, such as NAT traversal or route solving and then put the remote objects transport over that.
It is not a short term project, so at this moment I am only retrieving ideas and putting them in order.

In addition, thank you, again.

Are you GAY?
Are you a NIGGER?
Are you a GAY NIGGER?

If you answered "Yes" to all of the above questions, then GNAA (GAY NIGGER ASSOCIATION OF AMERICA) might be exactly what you've been looking for!