Lancejust that I wish there were easily available SDP parsers
stpeterin what languages?
LanceJS and Python
stpeterI'm kind of surprised we don't have one in JS given all the WebRTC work happening
LanceI've seen some partial works for that
LanceI think Phono might have a good implementation, not sure on licensing though
Lancebut the SOX idea is looking reasonable
stpeterLance: ugly but practical, yes
stpeterLance: I didn't write it up yet, but I think I will before the end of this week
Lanceright, just one more thing in the disco stack to check
stpeter:)
Lancesupport sox? use that. support jingle? use that
stpeterright
stpeteranyway I will run it up the flagpole and see who salutes :-)
KevAm I being dense that I don't immediately know what sox is?
Lancesip/sdp over xmpp
KevI've completely missed this.
KevWherewhowhywhatnow?
Lanceit was mentioned at the summit
Lancethe main issue is with the direction that webrtc has gone
stpeterKev: Lance and I had a chat about it here the other day
Lancewhich has standardized on using SDP
stpeterfishes out the logs
KevI must have not been in that track.
KevUnless you mean cusax (sp?)
stpeterhttp://logs.xmpp.org/xsf/130506/#20:27:18
stpeterKev: not CUSAX
Lanceso browser apps right now just pass SDP blobs around to set up video/audio sessions
stpeterCUSAX is Combined Use of SIP and XMPP = dual-stack clients
Lanceand browsers dont provide a way to parse or get the raw data in the SDP blob
stpeterSoX is for XMPP-only endpoints to send plain SDP
Lanceso just lots of error prone parsing/translating back and forth to jingle
stpeterwow, I haven't logged into stpeter@jabber.org for a while -- I have 100+ buddy requests
KevThis sox stuff doesn't sound very appealing!
LanceKev: yes, very ugly and blobby
Lancebut also simpler for certain useful cases
KevI hope we're putting it inside the message body!
Lanceand JSON encoding it, for good measure
stpeter:)
stpeternice! ".stpeter@jabber.org would like to subscribe to your presence"
stpeterKev: in fact, SoX is just about the ugliest thing you've ever seen, but it works -- it's really http://xmpp.org/extensions/inbox/zoep.html revisited
KevSo you mean I might expect to see things as beautiful as http://xmpp.org/extensions/inbox/zoep.html#examples-call?
KevBecause that's what I've always thought has been missing from life.
KevThat example's also illegal, isn't it?
Lanceyep, with the < in the headers
stpeterI haven't looked at the ZOEP thing in a long time
KevFrom what I can tell, you're missing out.
stpeter:P
Lloydhas left
Alexhas joined
Lancehas joined
kevinhas left
kevinhas joined
Lancehas joined
Lancehas left
Lancehas joined
Lancestpeter: I also started on a xep for letting a server prep jids a client sends it: http://legastero.github.io/customxeps/extensions/jidprep.html
stpeterLance: ah, good, I've been thinking a lot in the last 24 hours about some Python code for internationalization, but only to output the codepoint tables for IDNA2008 and PRECIS
stpeterof course, Matthew Wild would say I should do it in Lua ;-)
MattJhas joined
stpeterspeaking of whom! ;-)
MattJHello!
stpeterbut multiple implementations are a good thing
stpeterMattJ: the topic is a server-side service that preps JIDs for you
MattJbookmarks the room, because one can never have enough bookmarks
stpeterheehee
MattJWant one? I can code it in about 5 minutes :)
stpeterMattJ: for some reason, Lance and I and a few others seem to use this room for technical discussions at times
stpeterMattJ: you can code most everything in 5 minutes :P
MattJTrying to move jdev out of prosody@?
stpeterjdev is dead, long live jdev!
MattJHeh
stpeterbesides, muc.xmpp.org isn't hammered like conference.jabber.org
stpeterand I'd assume that XSF IPR rules apply here, for whatever that is worth
MattJRules, pft
stpeterthat's the spirit!
MattJDo you also want the server to split it perhaps? or only prepping?
stpeterprepping seems like enough
stpeterthe client could send whole JIDs or only JID-parts
stpeteras Jack pointed out in the related email thread a while back, that doesn't help you until you're connected to the XMPP server, so one might want to offer an HTTP service as well, but IMHO the XMPP service would be a fine start
Lanceyeah, an HTTP service would be nice, but at that point, a whole heck of a lot of XMPP data would be nice to have exposed over standardized REST calls
stpeterheh
stpeterit's an open question how much really needs to go over XMPP -- many IQ things could happen over HTTP (oh, say, vCard get)
MattJHTTP? You're moving the goalposts :P
MattJadds, because it's only another couple of lines...
stpeterglances at PEP-0008
MattJLance, GET or POST?
LanceMattJ: I'd say just prepping the JID as given is enough. Clients can split them pretty easily
LanceGET should work
Lancecacheable
Lancestpeter: If you figure out getting precis to work in Python, i'll bundle it in to sleek
stpeterLance: it's a deal!
stpeterLance: but step one is to at least figure out how to output the tables I need -- that might lead to a building block we can use
stpeterI'm going to experiment with literate programming in my i18n program, we'll see how it goes :-)
Lancethe only problem I ever had with literate programming was that none of the systems worked like I wanted it to
Lancei think its a rite of passage, making your own literate programming framework
stpeterwho needs a system?
stpeterheh
stpeterand it's in the inbox
Lance\o/
Lanceand now I don't have to feel bad about not bundling Mbs of character data to stringprep in the browser
stpeterhehe
MattJ:)
stpeterindeed
stpetermake the server do all that work
MattJLong live simple clients
stpeter:)
stpeterthat brings me back to Jingle and SDP and SoX -- what I had always hoped for was a way for the client to tell the server "hey I want to call Alice" and the server would work out all the details -- the whole offer/answer model is so complex...
Lanceyeah, that would be nice
stpeterprobably just a dream :-)
Lancemaybe, but sox is pretty close
stpeterreally? I don't think so
stpeterSoX is just an ugly workaround for offer-answer madness
Lanceespecially since most clients just use a web view anyway which will eventually have webrtc support
stpeterbut it's within that same paradigm
stpeterhmm, maybe
Lancejust grap the sdp blob, send, be happy
stpeteryou're more of an optimist than I am :P
Lanceprobably
Lancebut its looking like webrtc will hopefully solve a lot of these problems and pave the road
stpeternod
stpeterI still worry about silos
stpeterbut I suppose I always will
Lancei dont think sox would be any more siloable than things already are