..Net remoting is a good place to start. I would start your research there.
If you go this way, you may also want to try copying your object from one
application to another first. Many of the same skills are required and you
wont have to hassle with two machines at first.
More information:
I always find it helpful to think of networking in terms of the layering of
increasing complex protocols. You need to make sure that your communication
is established properly at the lower levels before moving to the higher
levels. The first thing you need is a physical connection between the two
machines (like a network cable). Then you need a way to pass generic
information between machines like tcp/ip. Then you will want to layer more
complex protocols on top of this to accomplish your task. The complexity of
each layer has resource and performance costs that need to be weighed
against available resources and performance requirements. Lower level
protocols will most likely be faster, less resource intensive, and more
versatile, but require more effort to implement and are harder to read when
revisited.
That being said it is important to understand your problem space. You want
to send an object from one computer to another. However, you are really not
sending an object from one computer to another. You are making a copy of an
object from one computer on another computer. If you have the class
definition on both machines then you can create an object instance on both
machines. Then you need to transmit the state of the source object from one
machine to the other and update the state of the destination object with
that state information. You will need to take your source object and
serialize its state into a data stream. You are basically packaging it in a
compact form for transmission across the wire. When it goes across the wire
you will then want to reassemble it into a usable form, i.e. your object.
You would have to perform a similar operation even communicating from one
program to another. Obviously you wouldn't be sending object state across
machine boundaries, but you would be sending it across process boundaries.
There are technologies that perform this type of action in one form or
another depending on the needs of the application and the environment in
which your objects will communicate. .Net remoting is one of those
technologies. It provides you the ability to work on a copy of an object or
to appear to act on one object from different machines by updating the
original when the copy is acted on. There are a lot of problems inherent in
working on remote objects as if they were local. It is appropriate in
certain situations especially if you are in control of all aspects of the
system in which the objects are contained and there are not a ton of users
accessing the object. However, if the system is more spread out and the
environment not so controlled you may want to work with copies or consider
other alternatives. An evolving school of thought is Service Orientation or
SOA (Service Oriented Applications)
"Bill English" <nu****@comcast.net> wrote in message
news:CB**********************************@microsof t.com...
How do I send an object from one computer to another?
--
I am a 14 year old C# developer, I am completely self taught, so please
don't get mad if I ask a stupid question. Thanks.
