Re: [Uri-review] draft-merrick-jms-uri-01.txt

"Mark Baker" <distobj@acm.org> Thu, 28 February 2008 18:39 UTC

Return-Path: <uri-review-bounces@ietf.org>
X-Original-To: ietfarch-uri-review-archive@core3.amsl.com
Delivered-To: ietfarch-uri-review-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DCD1F28C97E; Thu, 28 Feb 2008 10:39:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.651
X-Spam-Level:
X-Spam-Status: No, score=-100.651 tagged_above=-999 required=5 tests=[AWL=-0.836, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622, HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9g2J6dPML2dj; Thu, 28 Feb 2008 10:39:13 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9BC033A6A7C; Thu, 28 Feb 2008 10:39:04 -0800 (PST)
X-Original-To: uri-review@core3.amsl.com
Delivered-To: uri-review@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A6D1428C794 for <uri-review@core3.amsl.com>; Thu, 28 Feb 2008 10:39:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Yk2cYjMyxCjJ for <uri-review@core3.amsl.com>; Thu, 28 Feb 2008 10:38:57 -0800 (PST)
Received: from el-out-1112.google.com (el-out-1112.google.com [209.85.162.179]) by core3.amsl.com (Postfix) with ESMTP id 5C41C28C475 for <uri-review@ietf.org>; Thu, 28 Feb 2008 10:38:54 -0800 (PST)
Received: by el-out-1112.google.com with SMTP id j27so4784941elf.25 for <uri-review@ietf.org>; Thu, 28 Feb 2008 10:38:47 -0800 (PST)
Received: by 10.114.178.1 with SMTP id a1mr9894654waf.135.1204223926622; Thu, 28 Feb 2008 10:38:46 -0800 (PST)
Received: by 10.114.150.8 with HTTP; Thu, 28 Feb 2008 10:38:46 -0800 (PST)
Message-ID: <e9dffd640802281038p37a4419cpf4bfd8fd74d46e1a@mail.gmail.com>
Date: Thu, 28 Feb 2008 13:38:46 -0500
From: Mark Baker <distobj@acm.org>
To: Eric Johnson <eric@tibco.com>
In-Reply-To: <47C5068C.509@tibco.com>
MIME-Version: 1.0
Content-Disposition: inline
References: <47B5F1D7.10808@tibco.com> <e9dffd640802152100w700128b1o798ff432549799b8@mail.gmail.com> <47C4F47D.2080609@tibco.com> <e9dffd640802262207w3a29b6f6t598f2e5f2fda33dd@mail.gmail.com> <47C5068C.509@tibco.com>
X-Google-Sender-Auth: 5bdfbd08de68b447
Cc: uri-review@ietf.org, SOAP over JMS <soapjms@progress.com>
Subject: Re: [Uri-review] draft-merrick-jms-uri-01.txt
X-BeenThere: uri-review@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Proposed URI Schemes <uri-review.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/uri-review>, <mailto:uri-review-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:uri-review@ietf.org>
List-Help: <mailto:uri-review-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/uri-review>, <mailto:uri-review-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: uri-review-bounces@ietf.org
Errors-To: uri-review-bounces@ietf.org

Hi,

On 2/27/08, Eric Johnson <eric@tibco.com> wrote:
> I wonder if we're talking about the same kinds of operations though:
> would the JMS operations be ones that could be invoked remotely?
> Because that's what the registration template is asking for, e.g. HTTP
> GET for http:, FTP RETR for ftp:, etc... A quick look at the JMS
> Javadocs for ConnectionFactory and Destination doesn't reveal any
> application layer operations such as those AFAICT.
>
>  I believe you're right, we do disagree on the "kind" of operations.  In
> your response above, you indicate that you're expecting an "application"
> layer operation, but Section 2.4 doesn't actually use that qualification.

Right.  But it does ask what operations can be performed on the thing
identified by the URI.  I don't think that leaves much room for
interpretation, whether or not you use the language "application layer
operation".

> While section 2.4 proposes HTTP as a model for a URI that provides such
> operations, I don't read it as excluding other models.  For a clear
> counterpoint, the current treatment of the "mailto" URI in RFC 2368 does not
> require the use of "SMTP", nor should it.  I can think of uses where email
> gets sent with IMAP, a local sendmail agent, MAPI, or an HTTP web form (new
> in Firefox 3, I believe).  The "send" operation, then, is clearly decoupled
> from the application layer.

Avoiding "application layer" - sorry for muddying the waters with a
confusing term - yes, the send operation is the kind of operation
which should be documented with the registration.

>  On the "operation" front, our JMS proposal
> seems to be in good company.

Do you mean that jms URIs all identify resources to which one can send
data, ala email?  If so, then that's what you should document.

Mark.
-- 
Mark Baker.  Ottawa, Ontario, CANADA.         http://www.markbaker.ca
Coactus; Web-inspired integration strategies  http://www.coactus.com
_______________________________________________
Uri-review mailing list
Uri-review@ietf.org
https://www.ietf.org/mailman/listinfo/uri-review