I'd like some confirmation on something right now. Can someone tell me if I'm
right in the following examples:
where a is b's parent, and r is root? And am I forgetting anything?
OK, now to talk about a part of the Programmer's Guide that lost me:
"[...] The Jabber DTD is referenced from
Apologies to anyone who replied to my last post about namespaces, but I lost
about 50 e-mails this morning due to a system crash, so I'd appreciate, if
there were any replies, resends of those e-mails. Thank you.
-Kriggs
___
jdev mailing list
[EMAIL P
You can just look at the archives of the list, BTW :-)
- Dave
Kriggs wrote:
>
> Apologies to anyone who replied to my last post about namespaces, but I lost
> about 50 e-mails this morning due to a system crash, so I'd appreciate, if
> there were any replies, resends of those e-mails. Thank
On July 10, 2002 06:07 pm, you wrote:
> You can just look at the archives of the list, BTW :-)
>
> - Dave
*whacks himself*
:)
-Kriggs
___
jdev mailing list
[EMAIL PROTECTED]
http://mailman.jabber.org/listinfo/jdev
You might want to read this:
http://www.w3.org/TR/1999/REC-xml-names-19990114/
As well as the documents referenced from here:
http://www.jabber.org/ietf/
Peter
--
Peter Saint-Andre
Jabber Software Foundation
http://www.jabber.org/people/stpeter.html
On Mon, 8 Jul 2002, Kriggs wrote:
> I'd l
If you would like to help me (by reading these 90 lines of text), try your
best to correct me where I am wrong, and answer my questions (Lines marked
with an asterisk (*) are points which I especially am having trouble with):
1)
In this example, , and c="" are all using the
Kriggs wrote:
>If you would like to help me (by reading these 90 lines of text), try your
>best to correct me where I am wrong, and answer my questions (Lines marked
>with an asterisk (*) are points which I especially am having trouble with):
>
>1)
>
>
>
>
>
>In this example, , a
Thank you so much David! I know enough to continue on with my work. Now I'm
going to ask 8 questions that I see myself asking in the future. But first,
clarification on something David said.
> >* I notice that jabber:iq:auth has more than 1 colon (:). Is this only
> >possible for namespaces, or
I am writing a distributed computing system based on Jabber, and have been
building it from the ground up as I decided that no existing libraries
quite suit my purpose. So I started writing an XML stream library on top
of expat, and got it working just right. Namespaces work as specified by
the
Ari Johnson wrote:
>Looking at the jabberd code, it does indeed treat these as xmlns and
>xmlns:stream attributes on the element. Can anyone explain the reasoning
>behind this method, or if a fix might be possible without severely
>injuring the Jabber server itself? I really don't want to have
That's what I was afraid of, but I can deal with it, I'm sure. It's just
frustrating to write something and then realize when you're done debugging
it that you overlooked this kind of thing. Then again, jabberd is
significantly bigger than my code thus far, and it suffers that same
problem, rig
David Waite writes:
> In short, I don't think it is really anything that can be cleverly
> hacked in. Either a lot of things will break, or a lot of logic will
> need to be added for supporting legacy clients/servers. It has been off
> and on the roadmap for the open-source server, but I don't bel
Hi David!
David Waite wrote:
> This (together with the 'jabber:server' / 'jabber:component:accept'
> namespace usage) would be rather difficult to fix at this point
> without breaking interoperability with nearly every client, server,
> and server component - many of these use custom parsers
On Mon, 15 Jul 2002, Matthias Wimmer wrote:
> Hi David!
>
> David Waite wrote:
>
> > This (together with the 'jabber:server' / 'jabber:component:accept'
> > namespace usage) would be rather difficult to fix at this point
> > without breaking interoperability with nearly every client, server,
14 matches
Mail list logo