You could try establish a connection between clients, but then you're traveling into the world of NAT negotiation. Just try sending the public address of a clients to all other clients.<br><br>If this is for gaming, bear in mind you should probably only send unimportant things directly from client to client such as voice. You still want to have the server as the authority over the game simulation.<br>
<br>If you're really interested in learning how to get passed NAT devices, google it or check <a href="http://en.wikipedia.org/wiki/NAT_traversal">http://en.wikipedia.org/wiki/NAT_traversal</a><br><br>/eBeran<br><br><div class="gmail_quote">
On Wed, Jun 11, 2008 at 10:46 AM, Bjørn Lindeijer <<a href="mailto:bjorn@lindeijer.nl">bjorn@lindeijer.nl</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">On 5/16/08, Ng Yao Kheng <<a href="mailto:ngyaokheng@hotmail.com">ngyaokheng@hotmail.com</a>> wrote:<br>
><br>
> Hi all,<br>
><br>
> Does anyone know how to send a message from a client to another client that<br>
> is both connected to the server? Appreciate with some example code.<br>
><br>
> Please advice. Thanks....<br>
<br>
</div>Uhm, you would just have to send the message to the server, and the<br>
server would have to forward it to the other client.<br>
<br>
If your architecture requires you to do this frequently, you would<br>
probably add something like a target client id to the start of each<br>
message you send to the server, so that the server just reads this<br>
first and can forward the message directly to the target client.<br>
<br>
Hope that helped.<br>
<br>
Regards,<br>
Bjørn<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>
</blockquote></div><br>