Based on your description alone, I spot a few potential problems with that approach.
1. What should the sender do when Sublime closes? How will it know that Sublime closes? Say, for example, that Sublime crashes (spoiler alert, it can't know). 2. Second, what should happen if you have multiple Sublime and/or multiple Maya's? I get that you use UDP rather than TCP to avoid having to wait for confirmation from a potentially dead Sublime, but I'm less sure about how elegant that actually is. Another way might be to instead of pushing updates *to* Sublime, I would pull *from* Sublime. You could let Maya build up a buffer of messages that got emptied at a regular (of on demand) basis. That would eliminate the risk of Maya pushing messages unnecessarily. The buffer could optionally include a timestamp for each message such that you could pull a particular range of dates, so as to not prevent others from receiving any, and to not receive doubles. This way worst case scenario is an endless buildup of this buffer internal to Maya that never gets emptied. To solve that, you could either periodically empty it from within Maya, or only allow a fixed number of messages in it. For multiple concurrent sessions; I'm assuming you deal with this already, otherwise I've got an idea or two for this as well! -- You received this message because you are subscribed to the Google Groups "Python Programming for Autodesk Maya" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/python_inside_maya/CAFRtmOCS_yUK_7tSEaxZCk6wgtadPwScZXoqcVVYnY02pqp7fQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
