| | 1 | = Mexlca - Expansion = |
| | 2 | |
| | 3 | Expand existing infrastructue to have more than 1 interpretation channel |
| | 4 | |
| | 5 | = Development Approaches = |
| | 6 | |
| | 7 | Leave everything as is, and just work on the mexcla.tac (twisted service) |
| | 8 | |
| | 9 | Build a form that creates the channel, and determines how many interpretation channels exist, using the mexcla.tac infrastructure. |
| | 10 | |
| | 11 | Revamp the whole fucking thing and use freeswitch webrtc Sip.js, this option may or may not require also using the mexcla.tac. |
| | 12 | |
| | 13 | == Everything in tact == |
| | 14 | === Pros === |
| | 15 | |
| | 16 | Easiest to accomplish |
| | 17 | |
| | 18 | Faster |
| | 19 | |
| | 20 | Keeps the same not perfectly beautiful interface. |
| | 21 | |
| | 22 | Not too much work |
| | 23 | |
| | 24 | === Cons === |
| | 25 | |
| | 26 | Not resolving current problems with mexcla (which might be a problem with the protocol) |
| | 27 | |
| | 28 | Does not improve sound quality. |
| | 29 | |
| | 30 | Does not improve development of webrtc. |
| | 31 | |
| | 32 | Does not fully integrate into our webrtc infrastructure. |
| | 33 | |
| | 34 | Limits user interaction. |
| | 35 | |
| | 36 | == Build webform for handling channel creation == |
| | 37 | === Pros === |
| | 38 | |
| | 39 | Allows better interaction for people hosting a call. |
| | 40 | |
| | 41 | Permits language designation for the specific interpretation channel, i.e. more info for callers. |
| | 42 | |
| | 43 | Helps expand functionality, specific to each call. |
| | 44 | |
| | 45 | Relatively easy to implement. |
| | 46 | |
| | 47 | Would allow for adding features (pads, irc, calc, presentation, chat) to the channel. |
| | 48 | |
| | 49 | === Cons === |
| | 50 | |
| | 51 | Would require work, more development and testing. |
| | 52 | |
| | 53 | Would create more bugs. |
| | 54 | |
| | 55 | == Revamp == |
| | 56 | === Pros === |
| | 57 | |
| | 58 | integrate live (video) and mexcla (audio) |
| | 59 | |
| | 60 | get to learn cool new things |
| | 61 | |
| | 62 | Tighter integration to freeswitch (probably) |
| | 63 | |
| | 64 | Perhaps better audio quality |
| | 65 | |
| | 66 | Would be using websockets. |
| | 67 | |
| | 68 | We'd be cutting edge!!!! |
| | 69 | |
| | 70 | perhaps better integration with live.m.o |
| | 71 | |
| | 72 | === Cons === |
| | 73 | |
| | 74 | Don't know what we're doing |
| | 75 | |
| | 76 | Possibly lots more bugs |
| | 77 | |
| | 78 | perhaps we end up revamping live.m.o too |
| | 79 | |
