Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 72358 invoked from network); 16 Oct 2005 00:20:54 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 16 Oct 2005 00:20:54 -0000 Received: (qmail 85755 invoked by uid 500); 16 Oct 2005 00:20:53 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 85693 invoked by uid 500); 16 Oct 2005 00:20:52 -0000 Mailing-List: contact dev-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache Directory Developers List" Delivered-To: mailing list dev@directory.apache.org Received: (qmail 85682 invoked by uid 99); 16 Oct 2005 00:20:52 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 15 Oct 2005 17:20:52 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of trustin@gmail.com designates 64.233.184.205 as permitted sender) Received: from [64.233.184.205] (HELO wproxy.gmail.com) (64.233.184.205) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 15 Oct 2005 17:20:52 -0700 Received: by wproxy.gmail.com with SMTP id i21so301543wra for ; Sat, 15 Oct 2005 17:20:30 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=pENBQBWE/7jBnlPqaFeeV7PYTViJERmSqopXIKNRYdVCLVcTwvl+p/y9ZRykUVsTecliY+YLHrz61YIi3Timtyu3wF+yoV2FkKMlyFgaUfohLiB1gGxMvzrD5QwYAyr4PMLQGqTd1dgJAh1+gsa8kCft8aCyEjQ351o436WtP1I= Received: by 10.54.86.6 with SMTP id j6mr1359930wrb; Sat, 15 Oct 2005 17:20:30 -0700 (PDT) Received: by 10.54.71.11 with HTTP; Sat, 15 Oct 2005 17:20:30 -0700 (PDT) Message-ID: <768dcb2e0510151720t62c606b9m@mail.gmail.com> Date: Sun, 16 Oct 2005 09:20:30 +0900 From: Trustin Lee To: Apache Directory Developers List Subject: Re: [mina] DatagramAcceptor RFE In-Reply-To: <1129387782.18963.22.camel@localhost> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_17013_20476700.1129422030450" References: <1129387782.18963.22.camel@localhost> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N ------=_Part_17013_20476700.1129422030450 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hello Alban, 2005/10/15, Alban Peignier : > > We're working on a Java peer-to-peer API with NAT traversal support. > We're thinking about using the (great) Mina API to control the transport > layer. > > http://wiki.tryphon.org/Kolaka_P2PNet > http://wiki.tryphon.org/Kolaka_P2PNet#NAT_Traversal > > Everything is fine for us, except a missing feature in the > DatagramAcceptor. Indeed we need to artificially send a response paquet > (when needed) from a DatagramAcceptor. With the JDK APIs, we have the > send methods to perform it. The DatagramAcceptor (logically) doesn't > provide a such thing. But there is no way to extend the DatagramAcceptor > to make it possible. > > Can we find a way together to make it possible ? You can use DatagramConnector to send message first before the remote peer send one. IoConnector connector =3D new DatagramConnector(); IoSession session =3D connector.connect( ... ); session.write(...); Thanks, Trustin -- what we call human nature is actually human habit -- http://gleamynode.net/ ------=_Part_17013_20476700.1129422030450 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hello Alban,

2005/10/15, Alban Peig= nier <alban.peignier@free.fr>:
We're working on a Java peer-to-peer API with NAT traversal support.
We'= re thinking about using the (great) Mina API to control the transport
la= yer.

http://wiki.t= ryphon.org/Kolaka_P2PNet
htt= p://wiki.tryphon.org/Kolaka_P2PNet#NAT_Traversal

Everything is f= ine for us, except a missing feature in the
DatagramAcceptor. Indeed we = need to artificially send a response paquet
(when needed) from a DatagramAcceptor. With the JDK APIs, we have thesend methods to perform it. The DatagramAcceptor (logically) doesn't
p= rovide a such thing. But there is no way to extend the DatagramAcceptor
to make it possible.

Can we find a way together to make it possi= ble ?

You can use DatagramConnector to send message fi= rst before the remote peer send one.

IoConnector connector =3D new D= atagramConnector();
IoSession session =3D connector.connect( ... );
session.write(...);<= br>
Thanks,
Trustin
--
what we call human nature i= s actually human habit
--
http://g= leamynode.net/ ------=_Part_17013_20476700.1129422030450--