aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/OpenSim/Region/ClientStack
diff options
context:
space:
mode:
authorJustin Clark-Casey (justincc)2011-12-13 20:42:39 +0000
committerJustin Clark-Casey (justincc)2011-12-13 20:42:39 +0000
commitb242ceda1e7599a8e71150f3fcc9f27a64d18828 (patch)
tree5f83477d214d48e32a2836b113591fe4cdb8848d /OpenSim/Region/ClientStack
parentGet rid of the 'lolcat' library asset. (diff)
downloadopensim-SC_OLD-b242ceda1e7599a8e71150f3fcc9f27a64d18828.zip
opensim-SC_OLD-b242ceda1e7599a8e71150f3fcc9f27a64d18828.tar.gz
opensim-SC_OLD-b242ceda1e7599a8e71150f3fcc9f27a64d18828.tar.bz2
opensim-SC_OLD-b242ceda1e7599a8e71150f3fcc9f27a64d18828.tar.xz
In AvatarFactoryModule.SetApperance(), perform ValidateBakedTextureCache() in the same thread rather than on another one.
The caller is already an async thread from LLClientView so this doesn't hold up the client. However, launching on a separate thread does remove the effect of m_setAppearanceLock This was potentially allowing two different SetAppearance threads to interfere with each other, though this probably rarely happens, if at all.
Diffstat (limited to 'OpenSim/Region/ClientStack')
-rw-r--r--OpenSim/Region/ClientStack/Linden/UDP/LLClientView.cs6
1 files changed, 4 insertions, 2 deletions
diff --git a/OpenSim/Region/ClientStack/Linden/UDP/LLClientView.cs b/OpenSim/Region/ClientStack/Linden/UDP/LLClientView.cs
index 7223438..9c86c74 100644
--- a/OpenSim/Region/ClientStack/Linden/UDP/LLClientView.cs
+++ b/OpenSim/Region/ClientStack/Linden/UDP/LLClientView.cs
@@ -575,8 +575,10 @@ namespace OpenSim.Region.ClientStack.LindenUDP
575 /// <summary> 575 /// <summary>
576 /// Add a handler for the given packet type. 576 /// Add a handler for the given packet type.
577 /// </summary> 577 /// </summary>
578 /// <remarks>The packet is handled on its own thread. If packets must be handled in the order in which thye 578 /// <remarks>
579 /// are received then please us ethe synchronous version of this method.</remarks> 579 /// The packet is handled on its own thread. If packets must be handled in the order in which thye
580 /// are received then please use the synchronous version of this method.
581 /// </remarks>
580 /// <param name="packetType"></param> 582 /// <param name="packetType"></param>
581 /// <param name="handler"></param> 583 /// <param name="handler"></param>
582 /// <returns>true if the handler was added. This is currently always the case.</returns> 584 /// <returns>true if the handler was added. This is currently always the case.</returns>