Re: How can an object send itself to a child?
nooneinparticular314159@yahoo.com wrote:
Ok. Let me rephrase the problem a little bit. The application is
expecting some data from the network. One object gets that data,
decodes it, and passes it on to a second object which decides what
action to take based on what was in the message. That second object
may need to tell the first object to write some data back out to the
network. To do so, it must put some data in the first object's
message queue, so that when it gets called, it will have data to write
out to the network. The first object will then immediately write the
data to the network and life will be good. The problem is that object
Well, I'd consider making separate Input and Output objects.
Considering that managing queues is pretty complicated in itself, I
don't see any reason to make your single parent object "double up" on
it's work load and do both.
That will also simplify your IO, I think, but "decomposition into
smaller chunks" is the main goal.
#2 must be able to reference object #1. If I implemented a listener
object of some sort, then that object would still have to reference
object #1 before object #1 itself is called by the main method.
Right. As Lew implied, initialize your objects first. Get all those
pointers established. Then, kick off the IO process and open the
port/file/stream/etc.