Mailing-List: contact dev-help@openmeetings.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@openmeetings.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <CACeMiA9OjAiNhxbJ+dGB5a_FTgtEdP2Wrht1NuOWo6+L1epv-w@mail.gmail.com>
References: 
 <CAJ0=vFDHd8R=ZoHKAEMtRZ+h+AcgyGmGvQqnBV7ap3xXjicNYg@mail.gmail.com>
	<CACeMiA9=GrFcet42P1Fbhb6io_PTmo-sBq7WOHdeczRi55WdsA@mail.gmail.com>
	<CAJmbs8i=7XiPzezvn6sQjLhMpsmtubXyN_YYtRY-DwY5bNXBSg@mail.gmail.com>
	<CACeMiA9OjAiNhxbJ+dGB5a_FTgtEdP2Wrht1NuOWo6+L1epv-w@mail.gmail.com>
Date: Tue, 5 Apr 2016 10:01:12 +0600
Message-ID: 
 <CAJmbs8jGRfvmC-L5+D6jmXqWZjFr=irozKMDsnAk=0+Es1M1Qw@mail.gmail.com>
Subject: Re: weekly report, gsoc 2016, preparation
From: Maxim Solodovnik <solomax666@gmail.com>
To: dev <dev@openmeetings.apache.org>
Content-Type: multipart/alternative; boundary=001a1145ade068dad6052fb4e5a8

--001a1145ade068dad6052fb4e5a8
Content-Type: text/plain; charset=UTF-8

Hello Sebastian,

Why I have proposed to use wicket+WebRTC:
1) it will be used "as is" in OM
2) it will be maintained mainly by wicket community
3) it creates jetty/tomcat webRTC application in 2 simple steps [1] [2],
and development can be focused on red5 enhancement. (no need to write JS,
CSS, setup server etc.)


[1] https://wicket.apache.org/start/quickstart.html
[2]
https://github.com/wicketstuff/core/wiki/Html5#webrtc-api-wicketstuff-700-m6

On Tue, Apr 5, 2016 at 4:27 AM, seba.wagner@gmail.com <seba.wagner@gmail.com
> wrote:

> @Maxim/Dmitriy: I am fine with whatever approach. However my concern is
> that our goal is to deliver the best possible outcome for OpenMeetings. A
> working prototype of a webRTC implementation. Which is stable enough so
> that we can start thinking about how to migrate and integrate it. And that
> is quite a job/not really easy. There is like a ton of issues to think
> about (performance/ browser compatibility/ technology stack/ firewalls/
> network latency/ low bandwidth scenarios/ 1:1 versus 1:1000 broadcaster and
> view scenarios)
>
> My concern is that getting this into Wicket we loose too much time on
> secondary goals. I would rather really start to identify the main goals of
> our project and then really tackle those. And my gut feel is that this
> won't be easy.
>
> Thanks,
> Sebastian
>
> 2016-04-04 16:37 GMT+12:00 Maxim Solodovnik <solomax666@gmail.com>:
>
> > Actually Wicket already has WebRTC component [1]
> > This is why I have recommended Dmitriy to use it. Tobias, the author of
> > component is very responsive and might help in tuning/fixing the
> component
> > :)
> > here is the discussion: [2]
> >
> > [1]
> >
> >
> https://github.com/wicketstuff/core/blob/master/wicket-html5-parent/wicket-html5/src/main/java/org/wicketstuff/html5/media/webrtc/WebRTC.java
> > [2] http://markmail.org/message/voxhtxgaorjiwbur
> >
> > On Mon, Apr 4, 2016 at 10:27 AM, seba.wagner@gmail.com <
> > seba.wagner@gmail.com> wrote:
> >
> > > Hi Dmitriy,
> > >
> > > I would not be bothered too much around Wicket. The stuff you are doing
> > is
> > > pretty much cutting edge JavaScript/browser specific. You do not want
> to
> > > waste endless amount of time to try to make the JavaScript fit into
> > Wicket.
> > >
> > > It would be more "nice" to have it also ready to use as a Wicket
> > component.
> > > But we probably would need to look at your JavaScript and then end up
> in
> > > trying to create a module or even contribute it to the Apache Wicket
> > > project. That process could be an entire project on its own.
> > >
> > > So yeah, I would be basically fine with a pure JavaScript
> implementation
> > > and then we try to figure out how to get it into Wicket in a later
> step.
> > >
> > > However I leave that up to you, whatever suits you/is most efficient to
> > > you.
> > >
> > > But your short term goals sound very useful.
> > >
> > > Regarding nodejs: This technology is currently not part of our stack.
> Do
> > we
> > > really need it for the successful implementation of this project ?
> > >
> > > Btw: It might be good if you CC Maxim/Me (seba.wagner@gmail.com)
> > directly.
> > > Those kind of reviews will be mostly Maxim's and my duty. It's kind of
> > more
> > > reliable to CC people directly if you already know the ones you need to
> > > poke.
> > >
> > > Thanks,
> > > Sebastian
> > >
> > > 2016-04-04 10:28 GMT+12:00 Dmitriy - <dima00782@gmail.com>:
> > >
> > > > Hi all.
> > > >
> > > > I've began to investigate in apache wicket and their implementation
> > > webRTC.
> > > > I've started from creating small application with wicket html5 video
> > tag
> > > > and nodejs server for this purposes.
> > > > I will fix my researches here -
> > > > https://github.com/Dima00782/wicketTraining.
> > > >
> > > > On this week I learnt basics in Wicket and configure nodejs servers -
> > > > stun/turn/signaling.
> > > >
> > > > My short-term plans are to make list of requirements of protocols for
> > > red5
> > > > server for webRTC supporting in Open Meetings.
> > > >
> > > > --
> > > > Regards,
> > > > Dmitry Bezheckov.
> > > >
> > >
> > >
> > >
> > > --
> > > Sebastian Wagner
> > > https://twitter.com/#!/dead_lock
> > > seba.wagner@gmail.com
> > >
> >
> >
> >
> > --
> > WBR
> > Maxim aka solomax
> >
>
>
>
> --
> Sebastian Wagner
> https://twitter.com/#!/dead_lock
> seba.wagner@gmail.com
>


-- 
WBR
Maxim aka solomax

--001a1145ade068dad6052fb4e5a8--