search

brandom / ngx-sails

A socket client for Angular (2+) applications that connect to a Sails socket.io API.
MIT License
7 stars 3 forks source link

Help with the repository #2

Open abalad opened 6 years ago

abalad commented 6 years ago

Hello @brandom , I work with Angular and I'm looking to migrate the backend to sails, but I need a library to use on the front end, in case I found yours.

But I wanted to be able to help you, because I need something that worked for a good period of time, so I'm willing to use your lib and help you with bug reports and new features.

brandom commented 6 years ago

This sounds great! I am actually using Angular on my next project but it has been put on hold for a time so this lib isn't getting much attention.

My original goal for v1 was to refactor to use sails.io.js and add additional tests around this. However, I think a better direction would be to refactor to allow any SocketIO compatible lib as I don't believe that my next project will be using sails after all.

Did you have any features in mind that would require a hard dependency on sails?

abalad commented 6 years ago

@brandom I was using FeatherJS, but I want to migrate to Sails, so what I would need to implement is something to authenticate users with Sails via Passaport (Local, JWT), because the LIbs that exist today are all out of date

brandom commented 6 years ago

I see. Looks like we are almost moving in opposite directions, hah. I am moving to microservices so the RAILS-like monolith (Sails) is what I am moving away from. I actually looked at Feathers as a migration path because of its service semantics. Out of curiosity, what has drawn you to Sails, or driven you away from Feathers?

Either way I am sure we can get this lib to be useful for both of us. To clarify my earlier statements I just want the lib to provide REST over web sockets with no hard dependency on the WS client. So it could still be used for Sails by adding sails.io.js + socket.io-client as deps and passing any Sails-specific config to Angular DI.

abalad commented 6 years ago

@brandom I understand. What got me away from Feathers is the need for more server-oriented and scalable features. Like Migrations, Vertical and Horizontal Scaling. Another question is about ORM, which in feathers you have to change the services and sometimes to the entire application, in case you want to change the database