You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, I like your rpc framework on top top primus.io. Awesome work! For now, I used in my project dnode rpc with shoe on top of sock.js. I would like to migrate to eureca.io but I need that a server can responed multiple chunks to the client before the async "context.return()" method is called. This would be a kind of streaming, like in dnode or grpc. I know, for this purpose, it is possible do define a stub on the client side, which the server can callback for progress information, but I don't like the coding overhead to associate these client and server functions to each other. A "context.progress()" function would be really nice! On the client side a proxy stub call would callback a progress function passed as third argument to the promise: proxy.asyncServerHello().then( function(success) {}, function(error){}, function(progress){});
Best regards
Thomas
The text was updated successfully, but these errors were encountered:
Hello @the-duke and welcome to eureca.io :)
Actually I was thinking of an implementation of such solution, but I don't like to add a third callback to the promise, since it's not a standard.
there are many possible solutions, but this need reflexion to make the best solution which cover most of use cases.
Thank you for your fast reply an thinking about implementation. I use a lot of dojo toolkit and there the progress callback is passed as third argument. dojo/promise/Promise
But, while dojo might be not very common, i like your first solution with the finished argument.
Thank you a lot, i hope implementation is not too hard work for you.
Hello, I like your rpc framework on top top primus.io. Awesome work! For now, I used in my project dnode rpc with shoe on top of sock.js. I would like to migrate to eureca.io but I need that a server can responed multiple chunks to the client before the async "context.return()" method is called. This would be a kind of streaming, like in dnode or grpc. I know, for this purpose, it is possible do define a stub on the client side, which the server can callback for progress information, but I don't like the coding overhead to associate these client and server functions to each other. A "context.progress()" function would be really nice! On the client side a proxy stub call would callback a progress function passed as third argument to the promise:
proxy.asyncServerHello().then( function(success) {}, function(error){}, function(progress){});
Best regards
Thomas
The text was updated successfully, but these errors were encountered: