websocket connector for loopback

[joshua1]

will be nice to be able to specify REST or web sockets as the channel API to expose.for instance using socket.io or a loopback socket connector.
if there is a websockets-connector kind of plugin for loopback that will access the same methods exposed via the rest api via web sockets.

An important thing to consider: support in native SDKS - iOS, Android, Xamarin.

See also strongloop/strong-remoting#139

[dbryand]

+1

[michael-lee]

+1

[altsang]

duly noted, this is actually pretty high on our backlog and we hope to spike on it after our July release

[fotoflo]

+1

[telemakhos]

+1 for websockets support, and I think Primus would be a much better option since it allows you to effortlessly switch between real-time frameworks (Socket.io, Faye, SockJS, Engine.io, etc)

[gyss]

+1

[sandeshdamkondwar]

+1 I am excited to see websocket support

[dkarigithu]

• 1

[ghost]

+1

[luckymancvp]

I'm sorry. But currently we can't create realtime service with loopback.io. Is that right ?
Please tell me

[telemakhos]

@luckymancvp Well, you can, but you have to bake it yourself... see https://groups.google.com/forum/#!topic/loopbackjs/6qpQwggf2_c

[HansHammel]

+1

[steve8708]

+1

[nikita-leonov]

It was scheduled for 2.0 milestone. 2.0 released, did I get it right that it was rescheduled for further versions?

[bajtos]

Yes, I have removed the issue from the 2.0 milestone.

[yagobski]

+1

[coodoo]

I just started working on a lightweight real-time notifier based on loopback model, will post here when it's done.

[yagobski]

Thanks When you think it will be released?

[vvhh2002]

+1

[johnwook]

+1

[altsang]

sounds great @coodoo , there's a spike on @ritch 's plate to do a websocket integration to strong-remoting. Keep in mind this is where we have protocol pluggability starting with REST for making APIs in the flavor and transport that you're expecting. Once that spike actually gets scheduled in our sprint I'll be sending a heads up to LoopBackJS

thx again!

[robotiko]

+1

[valentinkostadinov]

+1

[lennybr]

+1

[Ijmir]

so it is not going to be in sprint 65?

[mattaylor]

+1 for https://github.com/gritzko/swarm

[altsang]

@ljmir - this capability has actually been rolled into a pub-sub feature that @ritch has been putting the finishing touches on, we're working on examples and docs at the moment - getting there folks! thx for your patience

[movibe]

thanks @altsang !

[altsang]

boy if you guys only knew how long this has been sitting in our backlog - 😛 , proof though that we really do keep tabs on stuff wanted/needed and try to work on them when we're not having to meet customer reqs

been a long time coming...

[telemakhos]

Fantastic! Going to try this is an financial ticker we're building rather soon... Thanks to the StrongLoop team! I guess these are the packages...

https://github.com/strongloop/strong-pubsub
https://github.com/strongloop/strong-pubsub-primus
https://github.com/strongloop/strong-pubsub-mqtt

thanks for the MQTT addition btw! this is an unexpected surprise

[altsang]

that is correct, I'm really glad we were finally able to get this in, we're very close

a lot of the use cases are driven by our exposure to early IoT customers, aside from websocket with a Primus interface, MQTT, we're looking at STOMP next and others

[altsang]

closing this issue, folks please see strongloop/strong-pubsub#7, @ritch is putting the finishing touches on it!

[theblang]

@altsang Wonderful news! Like @psi-4ward, this is essential for my application.

[altsang]

@mattblang - it's out there, @ritch blogged out what it does, the next step is to marry it up with our replication capabilities to better support use cases like offline sync w/o having it be client initiated, what are you building if I may ask?

[0x7b1]

+1

[theblang]

@altsang I am building a tracking system with Angular that uses WebSockets to stay synced across clients.

[theblang]

@altsang Is it correct if I say that right now MQTT is the only protocol supported for pubsub?

[altsang]

@mattblang strong-pubsub is protocol and transport independent. You can use your own protocol or the MQTT module we built. We're considering supporting STOMP next up depending on customer demand. For transport, you might be interested in Primus to take advantage of wrap around websocket support. You could even do MQTT packets through websocket using Mosquito adapter. For more info - https://strongloop.com/strongblog/introducing-strongloops-unopinionated-pubsub/.

[colceagus]

+1
What is the status on this issue development ?

[cyclops24]

+1

[vpedrosa]

+1

[pktippa]

+1 Much needed feature in loopback, atleast take this up in
https://github.com/strongloop/loopback-next

[bajtos]

@pktippa thank you for chiming in. Could you please open a new issue in https://github.com/strongloop/loopback-next to discuss the WebSocket server and/or client, depending on what you are looking for?

[pktippa]

@bajtos done!.

[bajtos]

Thanks. Let's move further discussion to loopbackio/loopback-next#1883 then.