lovetoxc14n do i need that in xmpp? do i need to read up on thatß✎
lovetoxc14n do i need that in xmpp? do i need to read up on that? ✏
dezanthas left
dezanthas joined
jubalhhas left
emushas joined
flowI don't think so, although discussions around canonicalization come up once in a while
flowbut with stanza routing hops may injecting new elements, modifying or deleted existing ones, it's probably unrealistic that c14n is in any sensible in xmpp
atomicwatchhas joined
marmistrzhas left
debaclehas joined
jgarthas left
spectrumhas left
kikuchiyohas joined
spectrumhas joined
jgarthas joined
lovetoxthanks
marmistrzhas joined
xeckshas joined
antranigvhas joined
rafasaurushas left
jgarthas left
Alexhas left
pasdesushihas joined
Alexhas joined
Ge0rGhas left
serge90has joined
huhnhas left
Ge0rGhas joined
rafasaurushas joined
Yagizаhas left
x51has joined
huhnhas joined
kikuchiyohas left
kikuchiyohas joined
lovetoxhm
lovetoxhow does xml:lang inheritence work with websocket?
lovetoxas every websocket frame is its own document i guess not at all
marmistrzhas left
lovetoxso am i supposed to add xml:lang to every message
lovetoxoh wow yes indeed thats how it works
lovetoxthat breaks everything, now i dont even have a document, just lose elementes ...
ZashDould have been nice do define a websocket variant without that framing hack
MattJYet people rejoiced at finally having framing, at the time
MattJand consider streaming the hack :)
lovetoxits just makes it really hard to abstract over these two different streaming methods
lovetox ..
flowmaybe that's just another argument to not view the XMPP connection of an endless stream of an XML document, but instead a stream of individual XML elements: the XMPP top level stream elements✎
ZashHrrrrrrrr
Kevflow: That's more or less what we do in M-Link, turn the document stream into a stream of top level elements. I imagine most things do the same.
MattJYes
debaclehas left
flowmaybe that's just another argument to not view the XMPP connection as an endless stream of an XML document, but instead a stream of individual XML elements: the XMPP top level stream elements ✏
Apollohas left
lovetoxem ... im not even sure how to do this
lovetoxhm
lovetoxbut then i lose all the nice things the parser does for me
lovetoxfor example i need then to add jabber:client to all incoming stanzas
lovetoxi need to do the same with xml:lang
lovetoxif i treat it as a document, the xml parser does this all for me
ZashMaybe you can do like what Prosody does, rewrite the websocket stream into an xmpp stream and parse that as usual
lovetoxyes, i plan to add a dummy <root> element
lovetoxi can even do <root xml:lang='en'>
lovetoxhm no i cant
lovetoxevery stanza needs to be its own document ..
lovetoxok lets leave websolcket broken for now :D
ZashThat does not sound like what prosody does.
kikuchiyohas left
flowlovetox, Smack wraps every top-level stream element in a synthesized <stream/> with the relevant attributes set. Since it's only a handful of attributes, it's pretty easy
kikuchiyohas joined
Alexhas left
flowof course, things get a little bit more complicated if you consider e.g. namespace declarations in <stream/>, but that should also be no show stopper
Apollohas joined
ZashUnless you rewrite `<open/>` into `<stream:stream>` and then feed everything into a normal stream parser
Alexhas joined
machas joined
debaclehas joined
dezanthas left
Wojtekhas joined
malthehas joined
marc0shas left
marc0shas joined
marc0shas left
marc0shas joined
Wojtekhas left
malthehas left
dezanthas joined
marc0shas left
marc0shas joined
marc0shas left
marc0shas joined
machas left
kikuchiyohas left
kikuchiyohas joined
Wojtekhas joined
jonas’has left
flowZash, what happens then?
ZashYou can pretend it's a normal XMPP stream and parse it as such