spider with mark
%spider-start and a vase containing
+$ start-args [parent=(unit tid) use=(unit tid) file=term =vase]
tidof parent thread if the thread is a child. If specified, the child thread will be killed with the parent thread ends.
tid(thread ID) to give the new thread. Can be generated with something like
(scot %ta (cat 3 'my-agent_' (scot %uv (sham eny)))). However you do it, make sure it's unique.
file- name of the thread file in
/ted. For example, if the thread you want to start is
vaseto be given to the thread when it's started. Can be whatever or just
!>(~)if it doesn't need any args.
[%pass /some-path %agent [our.bowl %spider] %poke %spider-start !>([~ `tid %foo !>(~)])]
spider with mark
%spider-stop and a vase containing
[tid ?], where:
tidof the thread you want to stop
?- whether thread should end nicely. If
%.yit'll end with mark
%thread-doneand the bunt value of a vase. If
%.nit'll end with mark
[%pass /some-path %agent [our.bowl %spider] %poke %spider-stop !>([tid %.y)]
Subscribe to thread result
Spider will send the result on
/thread-result/[tid] so you can subscribe there for the result. You should subscribe before starting the thread.
The result will have a mark of either
%thread-fail- has a vase containing a
termis an error message and
tangis a traceback.
%thread-done- has a vase of the result of the thread.
[%pass /some-path %agent [our.bowl %spider] %watch /thread-result/[tid]]
Subscribe to thread
You can subscribe to a thread on
/thread/[tid]/path. Note this is for facts sent off by the thread while it's running, not the final result. The path depends on the particular thread.
[%pass /some-path %agent [our.bowl %spider] %watch /thread/[tid]/thread-path]
To poke a thread you poke spider with a mark of
%spider-input and a vase of
tidis the tid of the thread you want to poke
cageis whatever mark and vase you want to poke it with
[%pass /some-path %agent [our.bowl %spider] %poke %spider-input !>([tid %foo !>('foooo')])]