1. ef948e6 [Chromoting] Introducing refcount-based life time management of the message loops in the service (daemon) and me2me host (network) processes. by [email protected] · 13 years ago
  2. efb972b Use a separate thread for audio capturing and encoding. by [email protected] · 13 years ago
  3. 56955a78 Always use chromium threads for IO in remoting host by [email protected] · 13 years ago
  4. c2c28ac4 Revert 148418 - Always use chromium threads for IO in remoting host by [email protected] · 13 years ago
  5. ead4940 Always use chromium threads for IO in remoting host by [email protected] · 13 years ago
  6. 3c8cfbe7 Use SingleThreadTaskRunner instead of MessageLoopProxy in remoting/host. by [email protected] · 13 years ago
  7. 95178556 Implement HostPortAllocator. by [email protected] · 13 years ago
  8. e6ed017 Move URLRequestContextGetter creation to ChromotingHostContext. by [email protected] · 13 years ago
  9. cec4d7a Add file thread in MessageHostContext. by [email protected] · 13 years ago
  10. c2b37440 Chromoting: Implemented security attention sequence (SAS) emulation on Windows. by [email protected] · 13 years ago
  11. f47f3bb59 Don't crash in ~HostNPScriptObject() when the object wasn't initialized. by [email protected] · 13 years ago
  12. e057e4b Use callback_forward.h instead of callback.h where possible. by [email protected] · 14 years ago
  13. 1eb55358 Cleanup: Remove unneeded forward declarations from remoting. by [email protected] · 14 years ago
  14. 195266b Add PluginMessageLoopProxy and use it for Host plugin UI thread. by [email protected] · 14 years ago
  15. cff9f37e Revert 97050 - Add PluginMessageLoopProxy and use it for Host plugin UI thread. by [email protected] · 14 years ago
  16. 12835bf4 Add PluginMessageLoopProxy and use it for Host plugin UI thread. by [email protected] · 14 years ago
  17. bfd9d5a Revert 96981 - Add PluginMessageLoopProxy and use it for Host plugin UI thread. by [email protected] · 14 years ago
  18. c47566d1 Add PluginMessageLoopProxy and use it for Host plugin UI thread. by [email protected] · 14 years ago
  19. 60fc9600 Use MessageLoopProxy for network message loop. by [email protected] · 14 years ago
  20. 2def95c Fix memory leaks in remoting_unittests. by [email protected] · 14 years ago
  21. a9cf9e7 Don't use base::OneShotTimer on plugin main thread. by [email protected] · 14 years ago
  22. 6d05197 Use the correct Chrome UI thread when creating the chromoting continue window. by [email protected] · 14 years ago
  23. 8f449bb Retrying submission of http://codereview.chromium.org/7144010/ by [email protected] · 14 years ago
  24. 217d63f Revert 89227 - Run DisconnectWindow::Show/Hide on correct thread. by [email protected] · 14 years ago
  25. f91ac53 Run DisconnectWindow::Show/Hide on correct thread. by [email protected] · 14 years ago
  26. 1a6cdf4 Make the UI-integration thread a non-UI thread in the Chrome sense. by [email protected] · 14 years ago
  27. 7b398be3 Run event executor on the ui thread to remove the need to explicitly XFlush() the XTest calls. by [email protected] · 15 years ago
  28. 1e72daa Resubmit "Fix crashes in ChromotingHost" by [email protected] · 15 years ago
  29. 34b9963 Move base/thread.h to base/threading, fix up callers to use the new location. by [email protected] · 15 years ago
  30. 708cd3c Remove capture thread in Chromoting host by [email protected] · 15 years ago
  31. 6fd3d6a1 Implement input stub in the host side for chromoting by [email protected] · 15 years ago
  32. 8ea7a167 This is a monster CL. by [email protected] · 15 years ago
  33. 8822f38c More FRIEND_TEST_ALL_PREFIXES. by [email protected] · 15 years ago
  34. 4d37c874 Refactor the client code for the X11 version. by [email protected] · 15 years ago
  35. afc05ab3 Start Chromoting Host Process in Chrome Service by [email protected] · 15 years ago
  36. 92698ce Fix thread usage in chromoting host by [email protected] · 15 years ago