Skip to content
Snippets Groups Projects
  1. Apr 29, 2024
  2. Nov 10, 2015
  3. Mar 29, 2013
  4. Nov 15, 2012
    • Richard Linden's avatar
      SH-3406 WIP convert fast timers to lltrace system · 9d77e030
      Richard Linden authored
      cleaning up build
      moved most includes of windows.h to llwin32headers.h to disable min/max macros, etc
      streamlined Time class and consolidated functionality in BlockTimer class
      llfasttimer is no longer included via llstring.h, so had to add it manually in several places
      9d77e030
  5. Feb 08, 2011
  6. Oct 13, 2010
  7. Sep 21, 2010
  8. Aug 13, 2010
  9. Apr 23, 2010
    • Monroe Linden's avatar
      Add a way for plugins to send a message and block waiting for the response · 57a2a2be
      Monroe Linden authored
      This requires some cooperation between the plugin and the host, and will only work for specific messages.
      
      The way it works is as follows:
      * the plugin sends a message containing the key "blocking_request" (with any value)
      * this will cause the "send message" function to block (continuing to pull incoming messages off the network socket and queue them) until it receives a message from the host containing the key "blocking_response"
      ** NOTE: if the plugin sends a blocking_request that isn't set up to cause the host to send back a blocking_response, it will block forever
      * the blocking_response message will be handed to the plugin's "receive message" function _immediately_ (before the "send message" function returns)
      ** this means that the plugin can extract response data for use by the the code that sent the message (but is still blocked inside the "send message" call)
      ** NOTE: this BREAKS the invariant stating that the plugin's "receive message" function will never be called recursively, and the plugin MUST be prepared to deal with this
      * after the plugin finishes processing the blocking_response message, the "send message" function that was called with the blocking_request message will return to the plugin
      * any queued messages will be delivered after the outer invocation of the plugin's "receive message" function returns (as normal)
      
      Inside the viewer, the code can tell when a plugin is in this blocked state by calling LLPluginProcessParent::isBlocked().  LLPluginClassMedia uses this to avoid sending mouse-move and size-change messages to blocked plugins.
      57a2a2be
  10. Mar 16, 2010
    • Monroe Linden's avatar
      Added an "init" message in LLPLUGIN_MESSAGE_CLASS_MEDIA, and made... · ce242821
      Monroe Linden authored
      Added an "init" message in LLPLUGIN_MESSAGE_CLASS_MEDIA, and made LLPluginClassMedia queue it up before initializing its LLPluginProcessParent.
      Made all existing plugins send their texture_params message from this init message instead of the LLPLUGIN_MESSAGE_CLASS_BASE "init" message.  (This ensures that they won't start to receive 'size_change' messages until after the init has happened.)
      Added "set_user_data_path" and "set_language_code" messages to LLPluginClassMedia.
      Made webkit plugin deal with the new messages, when they're sent before it receives the media "init".
      Removed the user_data_path and language_code arguments from the init function calls throughout the hierarchy.
      Made LLViewerMediaImpl queue up the language code and user data path messages before initializing the media.
      
      Reviewed by Callum at http://codereview.lindenlab.com/687006 .
      ce242821
  11. Mar 12, 2010
  12. Feb 03, 2010
    • Tofu Linden's avatar
      CID-264 · 81bc33f0
      Tofu Linden authored
      Checker: UNINIT_CTOR
      Function: LLPluginProcessChild::LLPluginProcessChild()
      File: /indra/llplugin/llpluginprocesschild.cpp
      81bc33f0
  13. Dec 09, 2009
  14. Nov 30, 2009
  15. Sep 30, 2009
  16. Aug 27, 2009
Loading