thank you very much.
I must made a mistake .:D<br><br><div class="gmail_quote">2012/7/30 Lee Salzman <span dir="ltr"><<a href="mailto:lsalzman@gmail.com" target="_blank">lsalzman@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
It is not broadcasted to all peers. It is only sent to the address of peer A.<div class="HOEnZb"><div class="h5"><br><br><div class="gmail_quote">On Mon, Jul 30, 2012 at 10:39 AM, JiangHao <span dir="ltr"><<a href="mailto:jaxecn@gmail.com" target="_blank">jaxecn@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">correct my last mail : Why <span style="color:rgb(34,34,34);font-size:14px;font-family:arial,sans-serif">the content </span>
<span style="color:rgb(34,34,34);font-size:14px;font-family:arial,sans-serif">which is send to peer A</span> <span><font color="#222222" face="arial, sans-serif"><span style="font-size:14px"> is broadcasted to all peers </span></font></span> .Why not only directly to send to the peer A.<div>
<div><br>
<br><div class="gmail_quote">2012/7/30 JiangHao <span dir="ltr"><<a href="mailto:jaxecn@gmail.com" target="_blank">jaxecn@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>thanks for your reply .</div><div> my point is the same bufffers is send to the different address of the peers.because the function 'enet_socket_send' is called in a loop of the host's peers and the buffer argument of the function is allways 'host->buffers', </div>
<div> why the content is send to all other peer which is only send to peer A</div><div><div><br><br><div class="gmail_quote">2012/7/30 Lee Salzman <span dir="ltr"><<a href="mailto:lsalzman@gmail.com" target="_blank">lsalzman@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">The packet gets sent to the address of the peer, so it is thus received by the remote host. The packet is tagged with the id of the destination peer, so the remote host only has to index into its array of peers with that id. After, it compares the address in the peer with the address of the packet's sender to verify the packet came from the right source. There's no real performance penalty for this.<br>
<br><div class="gmail_quote"><div><div>On Mon, Jul 30, 2012 at 8:35 AM, JiangHao <span dir="ltr"><<a href="mailto:jaxecn@gmail.com" target="_blank">jaxecn@gmail.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div>
hello ,<div> I'm leaning the enet libaray,and i am puzzled with the flow of send buffer when i reading <div>the implementation of enet_protocol_send_outgoing_commands,</div><div> </div><div> here is: sentLength = enet_socket_send (host -> socket, & currentPeer -> address, host -> buffers, host -> bufferCount);<br>
<div> Is I made a mistake or you have it in the design? will it send the same buffers to all the peers of one host and filtered by </div></div></div><div>remote host when it has receved these buffers.?</div><div>
the performance is not affected if it is send to all <a href="http://peers.is" target="_blank">peers.is</a> it?</div>
<div> </div><div><br></div><div> forgive my poor english .and thanks for answer.</div><div> </div><div><br></div>
<br></div></div>_______________________________________________<br>
ENet-discuss mailing list<br>
<a href="mailto:ENet-discuss@cubik.org" target="_blank">ENet-discuss@cubik.org</a><br>
<a href="http://lists.cubik.org/mailman/listinfo/enet-discuss" target="_blank">http://lists.cubik.org/mailman/listinfo/enet-discuss</a><br>
<br></blockquote></div><br>
<br>_______________________________________________<br>
ENet-discuss mailing list<br>
<a href="mailto:ENet-discuss@cubik.org" target="_blank">ENet-discuss@cubik.org</a><br>
<a href="http://lists.cubik.org/mailman/listinfo/enet-discuss" target="_blank">http://lists.cubik.org/mailman/listinfo/enet-discuss</a><br>
<br></blockquote></div><br>
</div></div></blockquote></div><br>
</div></div><br>_______________________________________________<br>
ENet-discuss mailing list<br>
<a href="mailto:ENet-discuss@cubik.org" target="_blank">ENet-discuss@cubik.org</a><br>
<a href="http://lists.cubik.org/mailman/listinfo/enet-discuss" target="_blank">http://lists.cubik.org/mailman/listinfo/enet-discuss</a><br>
<br></blockquote></div><br>
</div></div><br>_______________________________________________<br>
ENet-discuss mailing list<br>
<a href="mailto:ENet-discuss@cubik.org">ENet-discuss@cubik.org</a><br>
<a href="http://lists.cubik.org/mailman/listinfo/enet-discuss" target="_blank">http://lists.cubik.org/mailman/listinfo/enet-discuss</a><br>
<br></blockquote></div><br>