Return-Path: Delivered-To: apmail-hadoop-core-user-archive@www.apache.org Received: (qmail 68541 invoked from network); 13 Oct 2008 11:57:38 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 13 Oct 2008 11:57:38 -0000 Received: (qmail 86356 invoked by uid 500); 13 Oct 2008 11:57:33 -0000 Delivered-To: apmail-hadoop-core-user-archive@hadoop.apache.org Received: (qmail 86319 invoked by uid 500); 13 Oct 2008 11:57:33 -0000 Mailing-List: contact core-user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: core-user@hadoop.apache.org Delivered-To: mailing list core-user@hadoop.apache.org Received: (qmail 86290 invoked by uid 99); 13 Oct 2008 11:57:33 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 13 Oct 2008 04:57:33 -0700 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of minslovey@gmail.com designates 209.85.134.189 as permitted sender) Received: from [209.85.134.189] (HELO mu-out-0910.google.com) (209.85.134.189) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 13 Oct 2008 11:56:25 +0000 Received: by mu-out-0910.google.com with SMTP id w1so1618674mue.9 for ; Mon, 13 Oct 2008 04:56:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type; bh=sHn+2gLTJYUyk/5CJR7lt0mSfC4N8JbBOKXOEB35q+k=; b=v/3Gbvh2arHscFkK6ky6oKNdRDiQ+LiRSg8R3lhg1t9AXV5XJh2hVskcCnVPpJiTHl oJwbyyQ50oGiuJV+pa7hvbKtZV6JO7AdvPkfK/Fq+F02PpIZQTCW61zunLBNlU5oL0S+ DFnlS1a2NcVbJqz+RY7ntOYNwNlsjTgnAQR3Y= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=BNuQ8pf61VfzsntJxRM02RlnMG+XokiF3lC1A7kiRnucgV+PICfD+24K2SDUHsCwRk EXqOnnNeZ979+jdngayObi6o97gaKWxeMiw6h9jewKD7UViAjbmZaSbMSkhsSQtQVIlS OAzwH3cX6eeRy6TZ8gRCCd2zNL2ru7ic33Ews= Received: by 10.142.47.13 with SMTP id u13mr33550wfu.38.1223899009651; Mon, 13 Oct 2008 04:56:49 -0700 (PDT) Received: by 10.142.187.3 with HTTP; Mon, 13 Oct 2008 04:56:49 -0700 (PDT) Message-ID: <196b15f70810130456x31a91c29n910e037d1ec73e92@mail.gmail.com> Date: Mon, 13 Oct 2008 20:56:49 +0900 From: "Min Cha" To: core-user@hadoop.apache.org Subject: If buffer is full after calling write? MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_150433_3168203.1223899009657" X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_150433_3168203.1223899009657 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi, I am using Mina2.0 for sending a simple message between servers. I am using the codes of tutorial level because I could have resolved my problems with tutorial example. That is, I did not set some properties for customizing the behaviors of Mina. Today, I have had an simple question about buffer problem. What happened if buffer is full after calling write on the tutorial example. Exception? Growing the buffer size automatically? Wait? Timeout? Thank you. Cheers. -- Min Cha, Dreaming Developer English : http://minslovey.blogspot.com Korean : http://minslovey.tistory.com ------=_Part_150433_3168203.1223899009657--