[Vishnu-developers] Fwd: Threads & Sessions revisited

[Mariano T. <mar...@fi...>]

Puede ser singleton porque registra propiedades de threads, asi que no jode 
que sea unica para la VM. Fijate que hice una clase en un nuevo paquete que 
se llama threading.


>Date: Sat, 03 Dec 2005 11:01:14 -0300
>To: Vishnu-developers
>From: Mariano Tepper <mar...@fi...>
>Subject: Threads & Sessions revisited
>
>Tal vez en vez de un mecanismo de suscripcion, deberiamos usar una clase 
>singleton que maneje el ThreadLocal. Esto es porque la API no garantiza 
>que el thread que recibe la notificacion, sea el mismo que la envia... En 
>la practica, usa el mismo thread, pero...
>
>"The order in which notifications will be delivered is unspecified. The 
>default implementation provided in the Observable class will notify 
>Observers in the order in which they registered interest, but subclasses 
>may change this order, use no guaranteed order, deliver notifications on 
>separate threads, or may guarantee that their subclass follows this order, 
>as they choose. "


-- 
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.1.362 / Virus Database: 267.13.11/191 - Release Date: 02/12/2005