On Tue, 2007-07-31 at 11:45 +0200, Alexander Gnauck wrote:
[EMAIL PROTECTED] schrieb:
And i expect all the major servers to get this right, because they
use xml parsers that are xml compliant¹...
this is assumption is wrong.
There is also many XMPP software which is using its own XMPP/XML
Hello,
Le 30 juil. 07 à 21:35, Peter Saint-Andre a écrit :
Sergei Golovan wrote:
Hi!
Today I've found some interesting commits in ejabberd SVN. It became
using [CDATA[ in XML output generation.
Is this acceptable according to RFC or no? I can't find any reference
in RFC-3920 except the
Ralph Meijer schrieb:
I am curious which software this holds for. Most XMPP implementations
are based on expat, as far as I know. Sure they might have their own
DOM's (my Twisted XMPP stuff does), but that is irrelevant for parsing.
There is many software which is using expat, but there is
Hi,
Not sure where the confusion was ... I always assumed that support for
CDATA was a given since it is just another xml construct.
Regards,
Mridul
Mickaël Rémond wrote:
Hello,
Le 30 juil. 07 à 21:35, Peter Saint-Andre a écrit :
Sergei Golovan wrote:
Hi!
Today I've found some
On Tue, Jul 31, 2007 at 01:28:43PM +0200, Alexander Gnauck wrote:
Today we talk about CDATA, hey but what is coming next?
Look the other way round: XMPP was supposed to use XML. Some first
implementation did namespaces and some other bit wrong because of
misunderstanding. So now we have some
Hello,
Le 31 juil. 07 à 13:58, Mridul a écrit :
Hi,
Not sure where the confusion was ... I always assumed that
support for
CDATA was a given since it is just another xml construct.
So am I. I have been surprise by the heated debate :)
--
Mickaël Rémond
http://www.process-one.net/
On Tue, Jul 31, 2007 at 01:28:43PM +0200, Alexander Gnauck wrote:
Ralph Meijer schrieb:
I am curious which software this holds for. Most XMPP implementations
are based on expat, as far as I know. Sure they might have their own
DOM's (my Twisted XMPP stuff does), but that is irrelevant for
On Tue, Jul 31, 2007 at 02:07:43PM +0200, Jacek Konieczny wrote:
[.snip.]
IMHO XMPP should become more XML compatible and not less. Both existing
XML parsers and serializers should be usable for XMPP. If something has
to be changed in the XMPP specification then it should be removing the
A small mistake I made:
On Tue, Jul 31, 2007 at 02:02:32PM +0200, Robin Redeker wrote:
On Mon, Jul 30, 2007 at 06:49:45PM -0700, Rachel Blackman wrote:
stream-send (
messagebody![CDATA[
Here:
+ chatwindow-get_message_from_user
+ ]]/body/message
);
data =
On Tue, Jul 31, 2007 at 05:22:50PM +0400, Sergei Golovan wrote:
The main mistake you did (and probably the only mistake, because CDATA
is indeed a valid XML construct) is that you BREAK THINGS.
Since NO software used CDATA before
Are you sure? Some people use existing XML libraries. Those
It was pointed out to me that the single-file feature in my proposal
can be a disadvantage in some cases, when large amounts of data are to
be transferred:
* Servers using DOM will need much memory
* It's harder to read and edit the data by hand
A possible alternative is to use the layout of the
Hello,
Le 31 juil. 07 à 15:22, Sergei Golovan a écrit :
The main mistake you did (and probably the only mistake, because CDATA
is indeed a valid XML construct) is that you BREAK THINGS.
Since NO software used CDATA before there's certainly some which
will break.
All software that use an
On Tue, 2007-07-31 at 17:22 +0400, Sergei Golovan wrote:
On 7/31/07, Mickaël Rémond [EMAIL PROTECTED] wrote:
Hello,
Le 31 juil. 07 à 13:58, Mridul a écrit :
Not sure where the confusion was ... I always assumed that support for
CDATA was a given since it is just another xml
On 7/31/07, Jacek Konieczny [EMAIL PROTECTED] wrote:
On Tue, Jul 31, 2007 at 05:22:50PM +0400, Sergei Golovan wrote:
The main mistake you did (and probably the only mistake, because CDATA
is indeed a valid XML construct) is that you BREAK THINGS.
Since NO software used CDATA before
Are
Sergei Golovan schrieb:
I wasn't clear enough here. I mean no sowtware generated XML with
CDATA. I can't count for all programs in the world, but all server
implementations use plain XML escaping.
i think this is solved now.
CDATA is in the RFC3923 which means the latest ejabberd commit is RFC
Right decision imho. :)
On 7/31/07, Alexander Gnauck [EMAIL PROTECTED] wrote:
Sergei Golovan schrieb:
I wasn't clear enough here. I mean no sowtware generated XML with
CDATA. I can't count for all programs in the world, but all server
implementations use plain XML escaping.
i think this
On Tuesday 31 July 2007 5:32 am, Robin Redeker wrote:
On Tue, Jul 31, 2007 at 02:07:43PM +0200, Jacek Konieczny wrote:
[.snip.]
IMHO XMPP should become more XML compatible and not less. Both existing
XML parsers and serializers should be usable for XMPP. If something has
to be changed in
Mridul Muralidharan wrote:
Peter Saint-Andre wrote:
Mridul Muralidharan wrote:
IMO, (un)escaping should only be done by the entities which need to do
so - we should not mix a routing construct with display.
Sure. We never mess with the routing. From the client perspective,
XEP-0106 is only
Sergei Golovan schrieb:
BTW, using CDATA in generating XML by ejabberd is optional now. I
think It's the best solution. If it increases performance then admins
of really big deployments could enable it themselves.
That's what I plan to do in jabberd14 as well. I think using CDATA to
compact
19 matches
Mail list logo
