-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 08/28/2012 10:23 PM, Peter Saint-Andre wrote: > On 8/28/12 2:03 PM, Jack Moffitt wrote:
(Note: this discussion this was on the members mailing list, but I am sending it to the summit and BOSH mailing lists, because I think it is most relevant there). >> If there are enough interested parties, I'd love to have a >> discussion about future directions of BOSH, or perhaps some kind >> of strophe-related sprint. > > We had some discussions last time (in Brussels) about HTTP/XMPP > integration, but I'm sorry to say they didn't really lead anywhere > because we all dropped the ball on follow up. Perhaps we could > pick up the ball again in Portland... Unfortunately I won't be able to make it to Portland for Summit 12, but I think it would be very good to discuss BOSH. So maybe it would be possible for me to participate in the discussion by some kind of tele-presence? I think there are two mayor topics to discuss: 1) Issues in the current protocol. A starting point for that is the list at: http://wiki.xmpp.org/web/BoshIssues (though that list needs some TLC from me). If we can identify the most important issues on there and a direction to fix them, then already much work is done. 2) Long term, the future of BOSH. In at summit 11 in Brussels the opinion was vented to abandon BOSH asap in favor of websockets. Though I think websockets should be superior to BOSH, I believe we are far from the point where we can switch to websockets. One of the reasons is beacuse the current extension for XMPP over websockets needs some serious polishing up, it is not adapted to the latest changes in the websocket protocol. So I think it would be good to take a moment time to think about our long term strategy and to look at who is able and willing to take on some of the tasks that inevitable come out of that. CU! Winfried -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iEYEARECAAYFAlBz2a0ACgkQcxyv01PBoy/h9ACfbRBo2wAzVr0MSPWjokUTWrLk /VUAoOiWkvaR8mWBtI2JMJu2u5B/S+be =T67F -----END PGP SIGNATURE-----
