How does a RemoteObject find its destination?

Question

I am new to Flex. I am a long time Java/C++/C developer so my head won't explode if we get technical.
I am trying to figure out how a RemoteObject finds it's destination with just a simple reference as "SomeDestId" configured on BlazeDS the app server.
From the client side I am used to getting a reference to some Registry like JNDI or whatever by stating which host and port to use or a URI or something more absolute. I am aware that the flash player has a sandbox so we can dispense with the host, we know what it has to be. But my question is. How does the swf file or the context of the flex app know where my BlazeDS is rooted in my J2EE app server if I don't tell it?
What am I missing? I have looked at the example code and have read the developer pdf but nobody talks about this.
Does BlazeDS start listing on a well known port other than the application server's port?
If not how is my flex program supposed to know what port BlazeDS is on?
Anyone know how this automagic works? Because I can't find it in the docs.
Does my SWF file need to be deployed from within the BlazeDS deployment if so I have missed where in the documentation this is stated.

Answer 1

Ok folks, I am aware of the channel sets and end points. These are configured in BlazeDS, the server side of this client/server arrangement. Everybody fixates on this server config. I got that.
But the client side is what I am fixated on.
Let us view the flash player as a virtual machine. More importantly a virtual machine that is not the same virtual machine that BlazeDS is running in which is running in a J2EE app server somewhere in the universe (hopefully in the same domain) but elsewhere in that domain EXACT location unknown to the client VM. Unless somebody has told the CLIENT where BlazeDS (the server) is somehow or some where.
From everybody's perspective there seems to be no separation in terms of Client/Server because all I get is its done on the server side config.
The client is asking it's virtual machine to return a reference to a RemoteObject at destination="LahDeeDah" not LahDeeDah@somehost:someport:somepath or what ever syntax you would care to use. This implies that "LahDeeDah" is registered in some kind of hashing registry that knows something about where BlazeDS is located and that it even exists.
How does the CLIENT swf program find this registry if I compile it in some IDE like Eclipse that is not aware that BlazeDS even exists somewhere? Remember, Channels and EndPoints are all configured on the server not in the CLIENT.
You folks keep talking about how to configure the server side. I want to know what mechanism allows the client to get access to this server side configuration. Remember this conf.xml is on the server not in my IDE or in the src that creates my SWF file.
As to an earlier post someone eluded to BlazeDS compiling the SWF file. No where in the docs did I see anything that said you MUST compile your src with BlazeDS and NOT some IDE like Flex Builder 3 which is what I am using.
Did I miss this somewhere? Or was this info supposed to be handed down through divine revalation?
Oh I give up! I'll just tear into the src and figure it out myself. It should be in the RemoteObject hierarchy.