Synchronous Requests

Cached Responses (Fast)

FireREST is designed to respond quickly to client requests without blocking. Work is performed in a background thread and results are made available to subsequent requests. This mode of operation relies on cached responses to minimize request latency and maximize scalability. By default, all requests use cached responses. Example:

http://firepick:8080/firerest/cv/1/gray/cve/calc-offset/process.fire

Synchronous, Blocking Requests (Fresh)

FireREST also provides synchronous blocking requests for key resources. Blocking requests guarantee that the request will use the most current information. However, blocking requests should be used sparingly and never for monitoring. To specify a blocking request, simply use /firerest/sync instead of /firerest in the URL:

http://firepick:8080/firerest/sync/cv/1/gray/cve/calc-offset/process.fire

The /firerest/sync and /firerest URLs always refer to the same resource. For example, if you change CVE properties using /firerest, the same properties will be available using /firerest/sync.

Although /firerest/sync can be used for any FireREST URL, only some resources support synchronous blocking:

• process.fire
• camera.jpg
• gcode.fire (POST)

FireREST/CV Test Page

Use the Service return parameter to test synchronous requests. Choose Fast or Fresh.