Return-Path: 
 <dev-return-5311-apmail-directory-dev-archive=directory.apache.org@directory.apache.org>
Delivered-To: apmail-directory-dev-archive@www.apache.org
Received: (qmail 54103 invoked from network); 6 Apr 2005 05:59:58 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 6 Apr 2005 05:59:58 -0000
Received: (qmail 20628 invoked by uid 500); 6 Apr 2005 05:59:56 -0000
Delivered-To: apmail-directory-dev-archive@directory.apache.org
Received: (qmail 20330 invoked by uid 500); 6 Apr 2005 05:59:55 -0000
Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@directory.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@directory.apache.org>
List-Post: <mailto:dev@directory.apache.org>
List-Id: <dev.directory.apache.org>
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Delivered-To: mailing list dev@directory.apache.org
Received: (qmail 20301 invoked by uid 99); 6 Apr 2005 05:59:54 -0000
X-ASF-Spam-Status: No, hits=1.0 required=10.0
	tests=DNS_FROM_RFC_ABUSE,RCVD_BY_IP,SPF_HELO_PASS,SPF_PASS,URIBL_SBL
X-Spam-Check-By: apache.org
Received-SPF: pass (hermes.apache.org: domain of trustin@gmail.com designates
 64.233.184.206 as permitted sender)
Received: from wproxy.gmail.com (HELO wproxy.gmail.com) (64.233.184.206)
  by apache.org (qpsmtpd/0.28) with ESMTP; Tue, 05 Apr 2005 22:59:52 -0700
Received: by wproxy.gmail.com with SMTP id 70so162771wra
        for <dev@directory.apache.org>; Tue, 05 Apr 2005 22:59:50 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references;
        b=mkJLy7MwaBXyV4k981E0XP2QwpWMY7x1a+FV8nVsXtAoaW/zQ3+Fqw+ixKtOZHdDUhuDkpGMtELUOX1z0vf6Rae74dYh+foVCUFdJqiMi10XUsT6P4hqecdBoeIdac1buyBoBQ2ocU4vtLZ6iKuukSW+ULVyLzhb/uU99ODqLWQ=
Received: by 10.54.71.15 with SMTP id t15mr312610wra;
        Tue, 05 Apr 2005 22:59:49 -0700 (PDT)
Received: by 10.54.70.20 with HTTP; Tue, 5 Apr 2005 22:59:49 -0700 (PDT)
Message-ID: <768dcb2e050405225929e0268c@mail.gmail.com>
Date: Wed, 6 Apr 2005 14:59:49 +0900
From: Trustin Lee <trustin@gmail.com>
Reply-To: Trustin Lee <trustin@gmail.com>
To: Apache Directory Developers List <dev@directory.apache.org>
Subject: Re: [mina] session.write() in sessionOpened()
In-Reply-To: <425353AB.3090609@thewallacepack.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
References: <4252E955.6060207@thewallacepack.net>
	 <425353AB.3090609@thewallacepack.net>
X-Virus-Checked: Checked
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N

Hi Richard,

Long time no see!

On Apr 6, 2005 12:12 PM, Richard Wallace <rwallace@thewallacepack.net> wrote:
<snip/> 

> Alright, turns out I was making a stupid mistake.  I had thought I had
> created a simple pass-thru encoder, but what I forgot to do was actually
> fill in the encode() method with any actual code to pass along the
> message.  So I got that all fixed up and my client is getting messages
> again, yay!

Good! :)

> Next question I have is what's the best way to start the services?
> Right now I'm using the SimpleServiceRegistry to start stuff and I
> thought this was great when I started using it cause of how easy it is.
>  But I'm already running into a few limitations, like I can tell the
> services what port to bind on, but I can't tell them what interfaces to
> bind on.  I also can't find a way to determine after binding what
> interfaces actually got bound to.

Good point.  I fixed Service class for users to specify a
SocketAddress instead of a port number.  If you've been using
ServiceRegistry, you'll have to change your code a little bit.

<snip/>

Hope this works. :)

Thanks,
Trustin
-- 
what we call human nature is actually human habit
--
http://gleamynode.net/