8b3fa3ed01
Going back to letting mailboxes use variable-length data. Note that this requires extra copies, so shared memory channels should be used for anything in the hot path. But this allows better RPC over mailboxes and other flexibility. Other changes: - added a j6::proto::sl::client class to act as a service locator client, instead of duplicating that code in every program. - moved protocol ids into j6/tables/protocols.inc so that C++ clients can easily have their own API
40 lines
1.3 KiB
Modula-2
40 lines
1.3 KiB
Modula-2
# Mailboxes are objects that enable synchronous IPC via arbitrary
|
|
# message-passing of tagged data and/or handles. Not as efficient
|
|
# as shared memory channels, but more flexible.
|
|
|
|
object mailbox : object {
|
|
uid 99934ad04ece1e07
|
|
|
|
capabilities [
|
|
send
|
|
receive
|
|
close
|
|
]
|
|
|
|
method create [constructor]
|
|
method close [destructor cap:close]
|
|
|
|
# Send a message to the reciever, and block until a response is
|
|
# sent. Note that getting this response does not require the
|
|
# receive capability.
|
|
method call [cap:send] {
|
|
param tag uint64 [inout]
|
|
param data buffer [optional inout]
|
|
param data_in_len size # number of bytes in data used for input
|
|
param handles ref object [optional inout handle list]
|
|
}
|
|
|
|
# Respond to a message sent using call, and wait for another
|
|
# message to arrive. Note that this does not require the send
|
|
# capability. A reply tag of 0 skips the reply and goes directly
|
|
# to waiting for a new message.
|
|
method respond [cap:receive] {
|
|
param tag uint64 [inout]
|
|
param data buffer [optional inout]
|
|
param data_in_len size # number of bytes in data used for input
|
|
param handles ref object [optional inout handle list]
|
|
param reply_tag uint64 [inout]
|
|
param flags uint64
|
|
}
|
|
}
|