Return-Path: 
 <dev-return-25310-apmail-directory-dev-archive=directory.apache.org@directory.apache.org>
Delivered-To: apmail-directory-dev-archive@www.apache.org
Received: (qmail 53960 invoked from network); 31 May 2008 02:56:34 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 31 May 2008 02:56:34 -0000
Received: (qmail 49388 invoked by uid 500); 31 May 2008 02:56:35 -0000
Delivered-To: apmail-directory-dev-archive@directory.apache.org
Received: (qmail 49354 invoked by uid 500); 31 May 2008 02:56:35 -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 49343 invoked by uid 99); 31 May 2008 02:56:35 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 30 May 2008 19:56:35 -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 akarasulu@gmail.com
 designates 209.85.198.224 as permitted sender)
Received: from [209.85.198.224] (HELO rv-out-0506.google.com) (209.85.198.224)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 31 May 2008 02:55:47 +0000
Received: by rv-out-0506.google.com with SMTP id g37so1514470rvb.25
        for <dev@directory.apache.org>; Fri, 30 May 2008 19:56:03 -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:sender:to:subject:mime-version:content-type:x-google-sender-auth;
        bh=Y+ZjlVZ4hAhL8BtTi6ncck1vvjI8KmMfRXe5kYkw11M=;
        b=BWpfBsdM9Wstb4KRhZeMBCEzEqTAZXpuW8M2RqIgiI5ysUd6Gi9ExfCulXVmDEgpHNS5S6sbSA1lonrnPgIec8j1WVhDjFlINhPq/UntLxVqlikhgwGQpgKIGKZnSIdUategx4JFkvsJXclwb+sNe144CvEs7MW/qnx5+O1AZ9U=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:sender:to:subject:mime-version:content-type:x-google-sender-auth;
        b=ghDjWHoQoWtxa/XKxlvc1Gw4P8985MvTjh79HBfjKf4psBUDfWzfKCHW/SMbPUYXKQzWa5KLTWEVziOBOAGmDYneodbW9704rsjGuNy7L1hh9D9+fhVqBHLNFvHi8fYOmKn1vtnL4S6UWKzr2AqZclKmlEcDv1TS9K7+gm0SZ80=
Received: by 10.140.250.14 with SMTP id x14mr949450rvh.79.1212202563876;
        Fri, 30 May 2008 19:56:03 -0700 (PDT)
Received: by 10.141.113.13 with HTTP; Fri, 30 May 2008 19:56:03 -0700 (PDT)
Message-ID: <a32f6b020805301956q2932f686kfc7be87ec289752@mail.gmail.com>
Date: Fri, 30 May 2008 22:56:03 -0400
From: "Alex Karasulu" <akarasulu@apache.org>
Sender: akarasulu@gmail.com
To: "Apache Directory Developers List" <dev@directory.apache.org>
Subject: [ApacheDS] Why would the OperationContext contain push and pop
 operations?
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_1550_7228229.1212202563877"
X-Google-Sender-Auth: 951621c0ac7551d1
X-Virus-Checked: Checked by ClamAV on apache.org

------=_Part_1550_7228229.1212202563877
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Just curious why we moved InvocationStack push and pop operations into the
OperationContext.  Can someone comment on this?

Thanks,
Alex

------=_Part_1550_7228229.1212202563877
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Just curious why we moved InvocationStack push and pop operations into the OperationContext.&nbsp; Can someone comment on this? <br><br>Thanks,<br>Alex<br><br>

------=_Part_1550_7228229.1212202563877--