Hi Dimitriy,

node.js for server-side js is a huge package that need to handled somehow... I also don't know if this would be the best solution...

webRTC browser2browser will not scale for private user and their dsl-connection. So webRTC or SIP/RTMP to a mediaserver that then multicasts to all peers sounds like a way to move away from flash... I think this is already discussed.

Anyway I have no experience in this area and I was wondering that this guy mentions a "simple solution".

Greetings Peter



Am 23.01.2017 um 11:58 schrieb Dmitriy -:
Hello Peter,

I'm working on webRTC native client that can accept peer connection from browser. We already have "serverlessmedia" solution "browser - to - browser" with our signal server in Java.

We're moving to "*peer*-to-*media server*-to-*all other peers*" solution.

>> Do you know this guy?
>> https://github.com/muaz-khan

Yeah, I know him, and even have tried to use his library recordRTC. Unfortunately, It allows to capture media stream ("live video") only in Chrome. Firefox just produces only one big chunk, IE/Edge doesn't support video etc. I tried many times to use pure JavaScript solution but libraries not ready for this purposes (MediaRecorder API and MediaSources API) yet and also our stack of technology doesn't permit to use JavaScript on the server side.

On Mon, Jan 23, 2017 at 5:41 PM, Peter Dähn <da...@vcrp.de <mailto:da...@vcrp.de>> wrote:

    I had a look around...

    I found this one...
    http://stackoverflow.com/questions/20056683/webrtc-multicast-one-to-many
    <http://stackoverflow.com/questions/20056683/webrtc-multicast-one-to-many>

    and the "simple solution can be peer-to-server model
    (*peer*-to-*media server*-to-*all other peers*)."

    Do you know this guy?
    https://github.com/muaz-khan

    Greetings Peter


    Am 23.01.2017 um 10:43 schrieb Peter Dähn:
    I thought the same about the general roadmap

    1st whiteborad (there was something in gsoc, right?)
    2nd audio/video (also gsoc but not finally prototyped)

    Lets have a look, if we could get some input (and feedback!) from
    such whish-list...

    Am 23.01.2017 um 10:33 schrieb Maxim Solodovnik:
    Wish list is good idea :)
    I guess it can be created from the list of JIRA issues, then
    discussed :)

    My plans were to perform next steps to remove Flash :),
    1) move WB to HTML5
    2) move Audio/Video ...
    last one seems to be tricky :( no POC yet :(


    On Mon, Jan 23, 2017 at 4:28 PM, Peter Dähn <da...@vcrp.de
    <mailto:da...@vcrp.de>> wrote:

        nothing critical, rooms are working so far...

        We will collect a few things regarding usability and look
        and feel. Unfortunatly by now no time is left... I think we
        will report this using Jira...

        btw.. Is there a kind of wish-list to discuss new
        features/wishes and probably get a ranking of things to
        implement or improve?

        Greetings Peter


        Am 23.01.2017 um 05:29 schrieb Maxim Solodovnik:
        If no critical issues will be reported, I plan to pack RC1
        on Wednesday
        Thanks for participating :)

        On Sat, Jan 21, 2017 at 10:48 AM, Maxim Solodovnik
        <solomax...@gmail.com <mailto:solomax...@gmail.com>> wrote:

            Or maybe even better to correct
            http://openmeetings.apache.org/themes-and-branding
            <http://ache.org/themes-and-branding>.html
            (Configuration -> User Interface -> Themes)
            And add section ....

            On Fri, Jan 20, 2017 at 11:56 PM, Maxim Solodovnik
            <solomax...@gmail.com <mailto:solomax...@gmail.com>> wrote:

                I can add the page to
                http://openmeetings.apache.org/
                <http://openmeetings.apache.org/>

                Configuration -> Customization -> Styling

                What do you think would it be OK?

                On Fri, Jan 20, 2017 at 9:22 PM, Peter Dähn
                <da...@vcrp.de <mailto:da...@vcrp.de>> wrote:

                    ok... is this Info somewhere? Maybe it is
                    enough to write it down in the documentation...


                    Am 20.01.2017 um 13:27 schrieb Maxim Solodovnik:
                    To provide custom styling/layout you can
                    modify existing css files ....
                    I can create empty "custom.css" and will add
                    it to be included last, but I see not much
                    sense in it ....

                    and you can do it as follows:
                    1) create webapps/openmeetings/css/custom.css file
                    2)
                    open 
webapps/openmeetings/WEB-INF/classes/org/apache/openmeetings/web/pages/BasePage.html
                    add link to your new CSS file

                    something like this :)

                    On Fri, Jan 20, 2017 at 6:15 PM, Peter Dähn
                    <da...@vcrp.de <mailto:da...@vcrp.de>> wrote:

                        one more thing: is it possible to provide
                        a custom.css file to provide custom layout
                        somehow?

                        Am 19.01.2017 um 06:42 schrieb Maxim
                        Solodovnik:
                        Hello All,

                        I believe 3.2.0 should be released, I'm
                        going to implement
                        https://issues.apache.org/jira/browse/OPENMEETINGS
                        <http://e.org/jira/browse/OPENMEETINGS>-1527
                        and would like to pack RC1

                        Please let me know if there are any
                        critical issues.
                        (you can use our demo for tests:
                        https://om.alteametasoft.com:8443/next
                        <http://t.com:8443/next>)

                        And IMHO we need to switch main stable
                        development branch to 3.2.x
                        3.1.5 can be released in a week or so
                        with some critical REST/SOAP fixes

                        WDYT?


-- WBR
                        Maxim aka solomax




-- WBR
                    Maxim aka solomax




-- WBR
                Maxim aka solomax




-- WBR
            Maxim aka solomax




-- WBR
        Maxim aka solomax




-- WBR
    Maxim aka solomax




--
Regards,
Dmitry Bezheckov.

Reply via email to