Locked Gripe: "stop" is very slow to take effect

Locked

  • Thursday, April 19, 2007 8:30 PM
     
     
    It takes a few seconds from hitting "stop" before it's actually stopped sharing -- this is a lot slower than it seems like it needs to be, given that presumably all you have to do (on the host end) is send out a "stopped sharing" message, clean up some memory, and call UnhookWindowsHookEx.

All Replies

  • Thursday, April 19, 2007 10:21 PM
     
     Answered

    Performance starting and stopping application sharing is currently under investigation for future releases.  Is the current perofrmance causing you concerns about security, or is this simply not meeting your expectations?

     

    Thank you for reporting on your experience,

     

    Brian Meek, Development Manager, Tahiti

  • Friday, April 20, 2007 4:40 AM
     
     
    It's not a security thing, it's just annoyingly slow -- I hit "stop", and the UI locks up while it's stopping; it then takes, timing it, 4 seconds before I can do anything else, which seems like more time than it should be taking.