hololinked.core.zmq.rpc_server.RPCServer
Bases: BaseZMQServer
The RPCServer
implements a infinite loop where ZMQ sockets listen for messages, in any transport layer possible
(INPROC
, IPC
or TCP
). Once requests are received, jobs are dispatched to the Thing
instances which are being served,
with timeouts or any other execution requirements (called execution context). Within the jobs, the requested
operation information is made available which is extracted and executed by a Thing
instance.
The results are then sent back to the client. Operations information include Thing
ID, the property, action or
event to be executed (events are usually PUB-SUB and are largely handled by the EventPublisher
directly),
what to do on them (readProperty
, invokeAction
etc.), the payload and the execution contexts (like timeouts).
This is structured as a JSON.
Jobs determine how to execute the operations on the Thing
instance, whether in queued, async or threaded modes.
This is their main function. Queued mode is the default as it is assumed that multiple physical operations in the physical world is not
always practical. Jobs also help the Thing
instance to retrieve operation information from a request object.
Default ZMQ transport layer is INPROC
, but IPC
or TCP
can also be added simultaneously. The purpose of INPROC
being default is that, the RPCServer
is the only server implementing the operations directly on the Thing
instances. All other protocols like HTTP, MQTT, CoAP etc. will be used to send requests to the RPCServer
only
and do not directly operate on the Thing
instances. Instead, the incoming requests in other protocols are converted
to the above stated "Operation Information" which are in JSON. INPROC
is the fastest and most efficient way to communicate between
multiple independently running loops, whether the loop belongs to a specific protocol's request listener or
the RPCServer
itself. The same INPROC
messaging contract is also used for IPC
and TCP
, thus eliminating the
need to separately implement messaging contracts at different layers of communication.
Therefore, if a Thing
instance is to be served by a well known protocol, say HTTP, the server behaves like HTTP-RPC.
Source code in hololinked\core\zmq\rpc_server.py
49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 |
|
Functions
__init__
__init__(*, id: str, things: typing.List[Thing], context: zmq.asyncio.Context | None = None, transport: ZMQ_TRANSPORTS = ZMQ_TRANSPORTS.INPROC, **kwargs: typing.Dict[str, typing.Any]) -> None
Parameters:
Name | Type | Description | Default |
---|---|---|---|
|
str
|
|
required |
|
List[Thing]
|
list of |
required |
|
Context | None
|
ZeroMQ async Context object to use. All sockets except those created by event publisher share this context. Automatically created when None is supplied. |
None
|
|
ZMQ_TRANSPORTS
|
transport layer to be used for the server, default is |
INPROC
|
|
Dict[str, Any]
|
tcp_socket_address: str
address of the |
{}
|
Source code in hololinked\core\zmq\rpc_server.py
run
Start the server. This method is blocking.
Creates job schedulers for each Thing
, dispatches each Thing
to its own thread and starts the ZMQ sockets
polling loop. Call stop() (threadsafe) to stop the server.
Source code in hololinked\core\zmq\rpc_server.py
stop
run_zmq_request_listener
Runs ZMQ's socket polling in an async loop. This method is blocking and is automatically called by run()
method. Please dont call this method when the async loop is already running.
Source code in hololinked\core\zmq\rpc_server.py
recv_requests_and_dispatch_jobs
async
Continuously receives messages from different clients and dispatches them as jobs according to the specific
requirements of a how an object (property/action/event) must be executed (queued/threaded/async).
Also handles messages that dont need separate jobs like HANDSHAKE
, EXIT
, timeouts etc.
Source code in hololinked\core\zmq\rpc_server.py
run_things
Run loop that executes operations on Thing
instances. This method is blocking and is called by run()
method.
Parameters:
Name | Type | Description | Default |
---|---|---|---|
|
List[Thing]
|
list of |
required |
Source code in hololinked\core\zmq\rpc_server.py
run_thing_instance
async
run a single Thing
instance in an infinite loop by allowing the scheduler to schedule operations on it.
Parameters:
Name | Type | Description | Default |
---|---|---|---|
|
Thing
|
instance of the |
required |
|
Optional[Scheduler]
|
scheduler that schedules operations on the |
None
|
Source code in hololinked\core\zmq\rpc_server.py
299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 |
|
execute_operation
async
classmethod
execute_operation(instance: Thing, objekt: str, operation: str, payload: typing.Any, preserialized_payload: bytes) -> typing.Any
Execute a given operation on a thing instance.
Parameters:
Name | Type | Description | Default |
---|---|---|---|
|
Thing
|
instance of the thing |
required |
|
str
|
name of the property, action or event |
required |
|
str
|
operation to be executed on the property, action or event |
required |
|
Any
|
payload to be used for the operation |
required |
|
bytes
|
preserialized payload to be used for the operation |
required |
Source code in hololinked\core\zmq\rpc_server.py
exit
Source code in hololinked\core\zmq\rpc_server.py
Attributes
id
str
instance-attribute
, writable
ID of the RPC server, used to direct requests from client. Must be unique.
For IPC & INPROC sockets, ID is used to create the socket as well. For TCP, it is used for
message routing.
things
List[Thing]
instance-attribute
, read-only
Thing
objects that will be served by this RPC server.
logger
logging.Logger
logger instance
req_rep_server
AsyncZMQServer
instance-attribute
, read-only
ZMQ server that handler request-reply pattern. Used for properties & actions.
event_publisher
EventPublisher
instance-attribute
, read-only
ZMQ servers that publishes events to clients in publish-subscribe pattern.
schedulers
tying.Dict[str, Scheduler]
instance-attribute
A map of thing ID to a Scheduler
object. For actions requiring special scheduling,
additional schdulers with ID "(thing ID).(action name).(opertaion)" is created.