Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Received-SPF: pass (athena.apache.org: domain of mueller@adobe.com designates
 64.18.1.183 as permitted sender)
From: Thomas Mueller <mueller@adobe.com>
To: Julian Reschke <jreschke@adobe.com>
CC: "dev@jackrabbit.apache.org" <dev@jackrabbit.apache.org>,
        =?iso-8859-1?Q?Michael_D=FCrig?= <mduerig@apache.org>
Date: Wed, 30 Nov 2011 13:46:19 +0000
Subject: Re: JSOP
Thread-Topic: JSOP
Thread-Index: AcyvZnCu7M7O2xTFTTCjaT6anb4JNA==
Message-ID: <CAFBF030.206D6%mueller@adobe.com>
In-Reply-To: <4ED6312D.7040903@adobe.com>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/14.13.0.110805
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Hi,

>Are we defining a protocol or an API?

A format: the JSOP format. For me that's the most important item. I don't
care too much about the protocol part - actually it doesn't need to be
standardized in my view (the HTTP protocol is sufficient). And the
MicroKernel API doesn't need to be standardized either (at least not at
the moment).

>My understanding was that we're
>talking about a remoting protocol that, yes, should use HTTP.

For Jackrabbit 3, the MicroKernel API is called from within the same
process, from the same computer, or remotely.

Regards,
Thomas