tag:support.arachni-scanner.com,2012-07-01:/discussions/questions/187-arachni-rpc-call-serviceoutput-returns-nothingArachni: Discussion 2013-04-03T15:43:51Ztag:support.arachni-scanner.com,2012-07-01:Comment/262047272013-04-03T15:43:50Z2013-04-03T15:43:50ZArachni RPC call "service.output" returns nothing?<div><p><code>service.output</code> is the same as
<code>framework.output</code>[1] whose docs say that these messages
are there to give some sense of process moving forwards but will be
wildly inaccurate and out of sync with what's actually
happening.</p>
<p>There's just no good way to store and transmit those messages as
they will easily go into the GBs and offer very little value.<br>
You can have those messages rerouted to a logfile for debugging
purposes but allowing transmission over RPC was a stupid idea and I
do apologize for luring you down that rabbit hole.</p>
<p>Which is why, as of v0.4.2 (which will go out once Rails 4.0
stable and some other deps are released), those output methods will
be deprecated.</p>
<p>I'll also introduce a much, much simpler API which will
hopefully make your life easier and which will be documented up to
its ears.</p>
<p>For now, prepare to get away from depending on the output
because you can't.</p>
<p>[1] <a href=
"http://rubydoc.info/github/Arachni/arachni/Arachni/RPC/Server/Framework#output-instance_method">
http://rubydoc.info/github/Arachni/arachni/Arachni/RPC/Server/Frame...</a></p></div>Tasos Laskos