g fluid objects makes the CLOS decoder essentially thread-unsafe.  (If every incoming JSON <code class="json">Object</code> is guaranteed to have a prototype with a <code class="json-literal">"lispClass"</code> member then there are no fluid objects and thread safety is ensured.)  If the user wishes to employ fluid objects in a threaded environment it is advisable to wrap the body of entry-point functions in <code class="api-name">with-local-class-registry</code>.</p>

  <div class="api_docstring">
  <p cla