What problem does it solve? Standard message queue consumers are fire-and-forget: you publish a task but never see the function's return value. This Skill shows how to enable funboost's RPC mode so publishers receive a task_id and can query the execution result, status, and success flag of any consumed task. ## Core Features & Use Cases - Synchronous RPC: Set is_using_rpc_mode=True in BoosterParams, then call func.push(...) to get an AsyncResult whose .result property blocks until the return value is ready. - Asynchronous RPC: Use await func.aio_push(...) to obtain an AioAsyncResult and await its .result or .status_and_result inside async code. - Query by task_id: Reconstruct AsyncResult(task_id) or AioAsyncResult(task_id) later to fetch status_and_result dictionaries or FunctionResultStatus objects. - Use Case: Build an HTTP API that submits a long-running background job via push(), stores the returned task_id, and lets clients poll an endpoint that reads AsyncResult(task_id).status_and_result to report progress and the final value. ## Quick Start Enable RPC mode on my funboost add function and show me how to push a task and block until its return value is available.
