[Council] VOTE: JEP-0077 (In-Band Registration)

Peter Saint-Andre stpeter at jabber.org
Wed Jun 18 12:57:23 CDT 2003


On Wed, Jun 11, 2003 at 09:49:45PM -0500, Ryan Eatmon wrote:
> 
> +1 assuming you fix that <registered/> problem

Yep, fixed that. I'm unsure about exactly how to document the behavior
if the user is already registered. Consider this example from the JPG:

******

Example 9-4. Server Response (already registered)

If the user is already registered with this service, the server would
respond back with the currently set information and an empty registered
element.

<iq type="result" from="aim.denmark" to="hamlet at denmark" id="1001">
  <query xmlns="jabber:iq:register">
    <registered/>
    <username>Hamlet</username>
    <password>gertrude</password>
    <key>
      106c0a7b5510f192a408a1d054150ed1065e255a
    </key>
    <instructions>
      Enter your AIM screen name and password.
    </instructions>
  </query>
</iq>

******

Notice that the current information is provided (presumably all the
required fields), along with <registered/> *and* <instructions/>. This
is the current behavior (although it seems that some implementations do
not include the password). Does the Council have preferences on how I
document this?

Peter




More information about the Council mailing list