Gajim - 2016-10-15

  1. lovetox im pretty sure now it has to do with nbxmpp
  2. lovetox on windows the stream ist just not read fast enough
  3. lovetox i decreased the read timeout to 10 millisecons
  4. lovetox and its fast as hell now
  5. lovetox before it was set to 200
  6. lovetox but why is linux behaving differently
  7. lovetox one clue could be that windows doesnt use the same queue then linux
  8. lovetox ..hmm i have no clue about network stuff..
  9. lovetox linus :)
  10. linus Something working on Linux but not on windows? You should know by now that my reaction to that will be "blame windows" :p
  11. juan Gajim has it's own e2e which is not OTR neither OMEMO, what is it? And how can I disable it from automatically starting?
  12. linus Probably OpenPGP!
  13. linus ?*
  14. linus Conversations supports it too
  15. linus But I don't think it "starts", you have to enable it manually I think
  16. Holger juan: It's XEP-0116.
  17. Holger juan: It can be controlled with 'autonegotiate_esessions' and 'enable_esessions' in the ACE.
  18. juan nice.. didn't know about xep 0116, I wonder why it's not more widely used
  19. lovetox haha :D
  20. lovetox
  21. linus nah
  22. zak Hmm... how do I read this... after some initial time you spend a negative amount of time learning with linux? ;-)
  23. zak ...but then, if you happen to survive, you will drive a bulldozer and ride over all those others who failed :)
  24. lovetox :D
  25. lovetox this whole socket stuff is too much for me
  26. lovetox where is the guy who wrote this stuff in nbxmpp
  27. tmolitor lovetox: maybe I can help with the socket stuff...
  28. Asterix it's a long long time dkirov wrote that. He is no more arround for a long time now
  29. lovetox tmolitor then turn on you windows vm and go :)
  30. lovetox in nbxmpp there is a class called IdleQueue
  31. lovetox windows and unix use different subclasses of that to send and receive data from the socket
  32. lovetox on unix there is GLib.io_add_watch used
  33. lovetox which basically looks on every gtk.main loop on the socket and sees if its open to write or receive
  34. lovetox and calls the appropriate functions for either
  35. lovetox so this is pretty fast, gtk main loop is basically all the time i think
  36. lovetox for windows there is another subclass because GLib.io_add_watch was not available for a long time
  37. lovetox it is now with a recent update to pygobject
  38. lovetox so what windows did until now is, create its own loop with GLib.add_timeout
  39. lovetox but only 200 ms timeout
  40. lovetox means we can only pull or send data 5 times per second
  41. lovetox which is incredibly slow
  42. lovetox now we could just reduce this to like 10 ms, but the much cleaner version would be to make it with io_add_watch possible
  43. lovetox for this to work you have to download the latest pygjobect stuff from github
  44. tmolitor lovetox: wouldn't this mean that the pygobject version in the windows build has to be updated to the newest version, too?
  45. lovetox yeah but that would be no problem :)
  46. lovetox talking about default branch of course
  47. lovetox for gtk2 there is no hope
  48. lovetox you could even add it yourself, the commit to is like 5 lines
  49. lovetox
  50. tmolitor oh...sounds nice...I'll have look once I've debugged some code for my own project...