DevTools/Actor Best Practices: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Created page with "Some aspects of front and actor design can be tricky to understand, even for experienced engineers. The following are several best practices you should keep in mind when addi...")
 
(Moved to devtools/docs/)
 
(9 intermediate revisions by one other user not shown)
Line 1: Line 1:
Some aspects of front and actor design can be tricky to understand, even for experienced engineers. The following are several best practices you should keep in mind when adding new actors and fronts.
Moved to https://github.com/mozilla/gecko-dev/blob/master/devtools/docs/backend/actor-best-practices.md
 
== Actor should clean up itself, don't wait for the client ==
 
In the past, some actors would wait for the client to send a "you are done now" message when the toolbox closes to shutdown the actor.  This seems reasonable at first, but keep in mind that the connection can disappear at any moment.  It may not be possible for the client to send this message.
 
A better choice is for the actor to do all clean up itself when it's notified that the connection goes away.  Then there's no need for the client to send any clean up message, and we know the actor will be in a good state no matter what.

Latest revision as of 13:19, 23 March 2017

Moved to https://github.com/mozilla/gecko-dev/blob/master/devtools/docs/backend/actor-best-practices.md

Retrieved from "https://wiki.mozilla.org/index.php?title=DevTools/Actor_Best_Practices&oldid=1166476"