[BXXPwg] Updated strawman for BEEP protocol URIs
Mon, 18 Jun 2001 21:59:34 -0700 (PDT)
I'm having a hard time understaning in what situation an application would
think "hmm, I have this endpoint, should I do IMXP or syslog-raw?" I mean,
even if it did both of those functions, wouldn't it know by context (eg
different fill-in fields in some config screen) that the particular
endpoint can be used for either profile?
The application is not making the decision - "here's an endpoint, whats
something interesting I can do with it". Rather, the logic is "I want to
do profile X, do I have an endpoint with which to do profile X"...
On Mon, 18 Jun 2001, Dan Kohn wrote:
> The initiator needs the URL, but the unique scheme names per profile are
> required if the listener is offering multiple profiles on the same port.
> A BEEP initiator is told by a URL to begin a session. The listener
> supports two profiles on the same port, IMXP and raw syslog. A
> hypothetical "beep" URL would not be able to specify which profile
> should be selected. But, an imxp or syslog.raw URL scheme name is by
> definition bound to a single BEEP profile, so there is no confusion over
> which profile to select.
> - dan
> Dan Kohn <mailto:email@example.com>
> <http://www.dankohn.com/> <tel:+1-650-327-2600>
> -----Original Message-----
> From: Gabe Wachob [mailto:firstname.lastname@example.org]
> Sent: Monday, June 18, 2001 21:48
> To: Dan Kohn
> Cc: email@example.com; Roy Fielding
> Subject: Re: [BXXPwg] Updated strawman for BEEP protocol URIs
> On Mon, 18 Jun 2001, Dan Kohn wrote:
> > The counterexample for Gabe is a beep listener that, for whatever
> > reason, supports profiles for two or more services on the same port.
> > Which is why I'd like to suggest the following (updated) proposal:
> Wait, why would a listener need a URL format? Only initiators are going
> need this URL containing a profile.. Only an initiator is going to have
> make a decision about *why* they are entering into a BEEP connection ..
> In other words, in BEEP, a "location" is not visible within the protocol
> if you talk to a BEEP endpoint (listener), that listener basically only
> cares really that you connected, and the negotiation for what profile to
> "execute" is part of the greeting and channel creation - no URL