Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

switch to can-connect-feathers #144

Closed
frank-dspeed opened this issue Feb 2, 2018 · 1 comment
Closed

switch to can-connect-feathers #144

frank-dspeed opened this issue Feb 2, 2018 · 1 comment

Comments

@frank-dspeed
Copy link

This example needs to switch to can-connect-feathers to use the new nativ feathersClient v3+ and it will change transport protocol soon so to keep track this demo should always use the client so this is abstracted.

can-connect-feathers will support with the next update dynamic loading of the feathersClient as promise based on condition to enable ssr with realtime again canjs/can-connect-feathers#104

@justinbmeyer
Copy link
Contributor

While can-connect-feathers is great, using feathers client is beyond what we want to show in one of the initial guides for DoneJS. DoneJS is intended to be not only node-framework acentric, but also backend language acentric.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants