Changes between Version 5 and Version 6 of mexcla-expansion


Ignore:
Timestamp:
May 28, 2014, 10:32:10 AM (7 years ago)
Author:
Jamie McClelland
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • mexcla-expansion

    v5 v6  
    55= Development Approaches =
    66
    7    Leave everything as is, and just work on the mexcla.tac (twisted service)
    8    Build a form that creates the channel, and determines how many interpretation channels exist, using the mexcla.tac infrastructure.
    9     Revamp the whole fucking thing and use freeswitch webrtc Sip.js, this option may or may not require also using the mexcla.tac.
     7 * Leave everything as is, and just work on the mexcla.tac (twisted service)
     8 * Build a form that creates the channel, and determines how many interpretation channels exist, using the mexcla.tac infrastructure.
     9 * Revamp the whole fucking thing and use freeswitch webrtc Sip.js, this option may or may not require also using the mexcla.tac. Or use nodejs (see https://github.com/englercj/node-esl). 
    1010
    1111== Everything in tact ==
    1212=== Pros ===
    1313
    14    Easiest to accomplish
    15    Faster
    16    Keeps the same not perfectly beautiful interface.
    17    Not too much work
     14 * Easiest to accomplish
     15 * Faster
     16 * Keeps the same not perfectly beautiful interface.
     17 * Not too much work
    1818
    1919=== Cons ===
    2020
    21    Not resolving current problems with mexcla (which might be a problem with the protocol)
    22    Does not improve sound quality.
    23    Does not improve development of webrtc.
    24    Does not fully integrate into our webrtc infrastructure.
    25    Limits user interaction.
     21 * Not resolving current problems with mexcla (which might be a problem with the protocol)
     22 * Does not improve sound quality.
     23 * Does not improve development of webrtc.
     24 * Does not fully integrate into our webrtc infrastructure.
     25 * Limits user interaction.
    2626
    2727== Build webform for handling channel creation ==
    2828=== Pros ===
    2929
    30    Allows better interaction for people hosting a call.
    31    Permits language designation for the specific interpretation channel, i.e. more info for callers.
    32    Helps expand functionality, specific to each call.
    33    Relatively easy to implement.
    34    Would allow for adding features (pads, irc, calc, presentation, chat) to the channel.
     30 * Allows better interaction for people hosting a call.
     31 * Permits language designation for the specific interpretation channel, i.e. more info for callers.
     32 * Helps expand functionality, specific to each call.
     33 * Relatively easy to implement.
     34 * Would allow for adding features (pads, irc, calc, presentation, chat) to the channel.
    3535
    3636=== Cons ===
    3737
    38    Would require work, more development and testing.
    39    Would create more bugs.
     38 * Would require work, more development and testing.
     39 * Would create more bugs.
    4040
    4141== Revamp ==
     42
     43More info: Freeswitch supports an [http://wiki.freeswitch.org/wiki/Mod_event_socket event socket model]. There are two kinds: outbound (this is how mexcla.tac works - you call freeswitch and press 6 and your are then sent to mexcla), inbound: an external application sends you commands and you pass them on to freeswitch.
     44
     45Having both is critical for mexcla.
     46
     47If we add inbound, and we write the application in nodejs, then it means your web browser can communicate with freeswitch over websockets - and ask questions like: who is in the conference? Who is talking right now? We can also send freeswitch commands, like mute this person, etc.
     48 
    4249=== Pros ===
    4350
    44     integrate live (video) and mexcla (audio)
    45     get to learn cool new things
    46     Tighter integration to freeswitch (probably)
    47     Perhaps better audio quality
    48     Would be using websockets.
    49     We'd be cutting edge!!!!
    50     perhaps better integration with live.m.o
    51     USi feels they can raise more money for this one
     51 * integrate live (video) and mexcla (audio)
     52 * get to learn cool new things
     53 * Tighter integration to freeswitch (probably)
     54 * Perhaps better audio quality
     55 * Would be using websockets.
     56 * We'd be cutting edge!!!!
     57 * perhaps better integration with live.m.o
     58 * USi feels they can raise more money for this one
     59 * Can provide standard conferencing tools - like ability to see who else is in the conference, mute people, etc.
    5260
    5361=== Cons ===
    5462
    55    Don't know what we're doing
    56    Possibly lots more bugs
    57    perhaps we end up revamping live.m.o too
     63 * Don't know what we're doing
     64 * Possibly lots more bugs
     65 * perhaps we end up revamping live.m.o too
    5866
    5967