API Question

["John D. Ament" <jo...@gmail.com>]

Hi all

So now I'm bugging you not from the incubator, but as a potential user :-)

I noticed within usergrid you have some form of push/websocket support.  I
am looking to deploy something to the cloud, with client consumers within
private networks (with external internet access).  I was hoping to use
websockets to power pushing between these remote clients as they'll be
exchanging data with one another.  It is a point to point type of
communication, so instead of generally "following" one client, I need to
specifically say who can follow who and what data is meant to go to that
client.  It seems though like there are some gaps with push support,
specifically if I look at [1] I notice you're using a custom websocket
transport layer over netty; but I'm not sure that it's quite finished.

Honestly, I was hoping to leverage Servlet 3.1 runtimes, e.g. Undertow,
Tomcat 8 or the like for websockets.  While netty's fast it ends up
requiring a second port over what you've already deployed to Tomcat.  Is
any of this possible?

John

[1]:
https://github.com/apache/incubator-usergrid/tree/master/stack/websocket

Re: API Question

[Nate McCall <na...@thelastpickle.com>]

Created https://issues.apache.org/jira/browse/USERGRID-226 so we can start
discussing this in earnest.

On Sun, Sep 7, 2014 at 8:11 PM, Ed Anuff <ed...@anuff.com> wrote:

> Hi John,
>
> Yeah, the Websocket stuff is very early and experimental.  There's two
> issues for implementing Websocket.  The first is how to implement the
> protocol, and at the time, I chose Netty because it was the easiest
> mechanism at the time to get something up and running.  The second issue is
> how to best handle the sorts of asynchronous stuff that makes Websocket
> interesting.  What we'd discussed to do was implement a "subscriptions"
> feature for listening to changes to collections and entities.  I think this
> is still the way we want to go but we had a bunch of refactoring of the
> persistence tier that had to get completed.
>
> Ed
>
>
>
> On Sun, Sep 7, 2014 at 7:58 PM, John D. Ament <jo...@gmail.com>
> wrote:
>
> > Hi all
> >
> > So now I'm bugging you not from the incubator, but as a potential user
> :-)
> >
> > I noticed within usergrid you have some form of push/websocket support.
> I
> > am looking to deploy something to the cloud, with client consumers within
> > private networks (with external internet access).  I was hoping to use
> > websockets to power pushing between these remote clients as they'll be
> > exchanging data with one another.  It is a point to point type of
> > communication, so instead of generally "following" one client, I need to
> > specifically say who can follow who and what data is meant to go to that
> > client.  It seems though like there are some gaps with push support,
> > specifically if I look at [1] I notice you're using a custom websocket
> > transport layer over netty; but I'm not sure that it's quite finished.
> >
> > Honestly, I was hoping to leverage Servlet 3.1 runtimes, e.g. Undertow,
> > Tomcat 8 or the like for websockets.  While netty's fast it ends up
> > requiring a second port over what you've already deployed to Tomcat.  Is
> > any of this possible?
> >
> > John
> >
> > [1]:
> > https://github.com/apache/incubator-usergrid/tree/master/stack/websocket
> >
>



-- 
-----------------
Nate McCall
Austin, TX
@zznate

Co-Founder & Sr. Technical Consultant
Apache Cassandra Consulting
http://www.thelastpickle.com

Re: API Question

[Ed Anuff <ed...@anuff.com>]

Hi John,

Yeah, the Websocket stuff is very early and experimental.  There's two
issues for implementing Websocket.  The first is how to implement the
protocol, and at the time, I chose Netty because it was the easiest
mechanism at the time to get something up and running.  The second issue is
how to best handle the sorts of asynchronous stuff that makes Websocket
interesting.  What we'd discussed to do was implement a "subscriptions"
feature for listening to changes to collections and entities.  I think this
is still the way we want to go but we had a bunch of refactoring of the
persistence tier that had to get completed.

Ed



On Sun, Sep 7, 2014 at 7:58 PM, John D. Ament <jo...@gmail.com>
wrote:

> Hi all
>
> So now I'm bugging you not from the incubator, but as a potential user :-)
>
> I noticed within usergrid you have some form of push/websocket support.  I
> am looking to deploy something to the cloud, with client consumers within
> private networks (with external internet access).  I was hoping to use
> websockets to power pushing between these remote clients as they'll be
> exchanging data with one another.  It is a point to point type of
> communication, so instead of generally "following" one client, I need to
> specifically say who can follow who and what data is meant to go to that
> client.  It seems though like there are some gaps with push support,
> specifically if I look at [1] I notice you're using a custom websocket
> transport layer over netty; but I'm not sure that it's quite finished.
>
> Honestly, I was hoping to leverage Servlet 3.1 runtimes, e.g. Undertow,
> Tomcat 8 or the like for websockets.  While netty's fast it ends up
> requiring a second port over what you've already deployed to Tomcat.  Is
> any of this possible?
>
> John
>
> [1]:
> https://github.com/apache/incubator-usergrid/tree/master/stack/websocket
>