Help with understanding applyAsync queue in the client

help
1

Im reviving a package from cult-of-coders called Fusion, it basically disconnects sockets by default and uses an http endpoint to run all methods. This will help with scaling on apps that dont require realtime or that dont require realtime on all pages.

I already have a working demo, but I can use some help to make it work with all methods like logingWith… or logout and I think what im missing is in how im recreating the applyAsync in the client.

@nachocodoner @grubba @fredmaiaarantes @gabsferreira

Will any of you guys be willing to give 15 minutes of your time to better understand how this works and create a robust alternative to sockets in meteor?

This is the package if you want to check it out GitHub - pmogollons/solar-sail

2 Likes
2

Well I got it working on my project. This will require some work before it can be used in any project.

But its a great proof of concept for what meteor could be able to do if this was part of the core. Ill probably do a demo of this at Meteor Impact.

2 Likes
3

I was able to load the socket stream client from the bundle which reduces its size by 90kb. This also opens the possiblity to recude the bundle size further by importing dinamically mini-mongo, allow-deny, geojson-utils and probably other packages that are only needed when using realtime data transport like ddp.