# appcalls and replies

=> veilid-3 previous
=> veilid-5 next

AppCalls seem to be like AppMesage, except that the receiving end will also get a call_id with the message.
the receiving end then seems to be expected to send an AppCallReply in response that uses the call_id instead of a route_id.
So there's at least this sort of bidirectionality.

I didn't get sending a reply to actually work, I just got an error message like
```
{"type":"Response","id":0,"op":"RoutingContext","rc_id":1,"rc_op":"AppCall","error":{"kind":"Timeout"}}
```
in the script I sent the AppCall with.

I'd first tested doing AppMessage with a few other options to see if it affected anything.
Not really.

by doing these before sending the appmessage:
```
{"op":"RoutingContext","rc_id":1,"rc_op":"WithPrivacy"}
{"op":"RoutingContext","rc_id":1,"rc_op":"Seqeuencing","sequencing":"EnsureOrdered"}
```

I dunno. I'm tired today.