WebAPI/2013-10-22

From MozillaWiki
Jump to: navigation, search


« previous week | index | next week »

WebAPI Meeting Details

  • Tuesday 2013-10-22 - 8:00 am Pacific
  • Dial-in: conference# 98413
    • People with Mozilla phones or softphones please dial x2000 Conf# 98413
    • US/Toll-free: +1 800 707 2533, (pin 369) Conf# 98413 (max 48 users at any time)
    • US/California/Mountain View: +1 650 903 0800, x2000 Conf# 98413
    • US/California/San Francisco: +1 415 762 5700, x2000 Conf# 98413
    • US/Oregon/Portland: +1 971 544 8000, x2000 Conf# 98413
    • CA/British Columbia/Vancouver: +1 778 785 1540, x2000 Conf# 98413
    • CA/Ontario/Toronto: +1 416 848 3114, x2000 Conf# 98413
    • UK/London: +44 (0)207 855 3000, x2000 Conf# 98413
    • FR/Paris: +33 1 84 88 37 37, x2000 Conf# 98413
    • sip:conf98413@mozilla.com or, for some clients, sip:conf98413@anonsip.scl3.mozilla.com (may not work for all rooms)
    • Gmail Chat (requires Flash and the Google Talk plugin): paste +1 650 903 0800 into the Gmail Chat box that doesn't look like it accepts phone numbers
    • SkypeOut is free if you use the 800 number
  • WebAPI Vidyo Room / London-Allo Allo / Toronto-Spadina
  • Join irc.mozilla.org #webapi for back channel

Notes below archived from etherpad: https://etherpad.mozilla.org/webapi-meetingnotes

Notes

  • Need Jonas or someone to take a look on the final proposal to support MMS Read Report, which has been in agreement with Gecko/Gaia engineers and W3C editors.
  • need a stream API
    • one need is for downloads (ex. potential loss of POST data if we hand off download)
    • want to be able to hand an HTTP connection off instead of just reconnecting to a URL
    • may need to do something proprietary (mozStream) for now since a short term standard is unlikely :/
    • Google has something that is like the Node stream API and it may work
    • Node community cautions that we shouldn't do something exactly like theirs
  • standardizing of web activities?
    • need to pull together information on what we've implemented and what we'd like to add in the future