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
If I have a procedure that returns a video, a photo or an mp3, a pdf or whatever. It would be cool to support java.io.File as a return type for Session.call().
For basic functionality the public API will basically be unchanged, no new overloading required. Unless we want to support some complex scenarios.
The text was updated successfully, but these errors were encountered:
om26er
changed the title
Session.call to return a file object
Session.call() to return a file object
Jul 20, 2017
I don't get this one. How would you fill this virtual java.io.File thing? I mean, eg from a Blob returned from a WAMP remote procedure call? If so, the WAMP procedure being called really should use progressive call results and progressively return chunks of bytes. And that should be fed into the file thing without rebuffering ideally.
You might then as well go as far as asking for the same thing but uplink;) That is, upload a big file from a virtual file thing to a remote WAMP procedure in a call argument. Yeah. Thing is, that is missing at the WAMP spec level still. Runs under the name "progressive calls". To differentiate from "progressive results".
If I have a procedure that returns a video, a photo or an mp3, a pdf or whatever. It would be cool to support
java.io.File
as a return type for Session.call().For basic functionality the public API will basically be unchanged, no new overloading required. Unless we want to support some complex scenarios.
The text was updated successfully, but these errors were encountered: