Client communication

To send RPCs on a session, you simply create an RPC, send it using nc_send_rpc(), and then wait for a reply using nc_recv_reply(). If you are subscribed, there are 2 ways of receiving notifications. Either you wait for them the same way as for standard replies with nc_recv_notif() or you create a dispatcher with nc_recv_notif_dispatch() that asynchronously (in a separate thread) reads notifications and passes them to your callback.

Functions List

Available in nc_client.h.

• nc_rpc_act_generic()
• nc_rpc_act_generic_xml()
• nc_rpc_getconfig()
• nc_rpc_edit()
• nc_rpc_copy()
• nc_rpc_delete()
• nc_rpc_lock()
• nc_rpc_unlock()
• nc_rpc_get()
• nc_rpc_kill()
• nc_rpc_commit()
• nc_rpc_discard()
• nc_rpc_cancel()
• nc_rpc_validate()
• nc_rpc_getschema()
• nc_rpc_subscribe()
• nc_rpc_getdata()
• nc_rpc_editdata()
• nc_rpc_establishsub()
• nc_rpc_modifysub()
• nc_rpc_deletesub()
• nc_rpc_killsub()
• nc_rpc_establishpush_periodic()
• nc_rpc_establishpush_onchange()
• nc_rpc_modifypush_periodic()
• nc_rpc_modifypush_onchange()
• nc_rpc_resyncsub()
• nc_send_rpc()
• nc_recv_reply()
• nc_recv_notif()
• nc_recv_notif_dispatch()