Alexey,
The point of service proxy is that you use your own API to do remote
invocations. I don't think that adding this generic "reflection-like" API
makes sense here. For asynchronous executions I would just use Compute Grid.
-Val
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Val,
My understanding is Krzysztof asks how to call a long-running service
asynchronously. It looks like right now Ignite does not support that.
What do you think about extending Ignite so that we could write something
like:
IgniteServices services = ignite.services();
AsyncServiceProxy asyncPr
Hi, thanks for clarification.
My use case it that I have some logic that is hidden from client but client
can execute this logic by calling Ignite Service.
Some of those operation may take a while, so I thought that it would be nice
to run it asynchronously and return Future object so the client
Krzysztof,
This will no work because service is invoked in server side and the returned
future gets serialized and sent to client. The deserialized instance is
obviously never completed. What are you trying to achieve?
-Val
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi Team,
I have a question regarding Ignite Services and Compute async.
If we have a deployed IgniteService like this
public class MySercviceImpl implements Service, MyService {
@IgniteInstanceResource
private Ignite ignite;
@Override
public IgniteFuture doStuff() {
IgniteFutu
