community 
Flushing outputs to the Sandbox Output console window - how to do this and avoid delays?
Hi All,
I am developing a CloudShell service for Wireshark. The idea is that you will be able to record and analyse packet traffic on virtual and physical resource interfaces within an active sandbox.
One issue I have is that long after I cancel a Service command, the messages still keep appearing in the Output window (I use the CloudShell API "WriteMessageToReservationOutput" command). I am currently printing out a message for every captured packet so how do I force the pending messages to be flushed faster?
Also, this begs the question of whether this is best practice? Should I build a complete response for the Service command and use the return option to print the output in one message.? Should I do the same for the complete response with the API? This has the benefit of not clogging the activity feed with 100's if not 1,000's of messages but it has the downside of the user having to wait until the command to complete until they see anything.
Any thoughts?
Thanks
Gary
Hi @Gary.W
While it might be nice to see the messages in the output window, you also need to be aware of these messages stored in the DB, so I'm not sure if that's something you'll want to have for the long run.
You can maybe just report some progress while the command runs, but at the end upload a file as an attachment to the reservation (which also stored in the db - but can be removed on teardown if not really needed).
Yaniv
