RFC: Changes to shared cacio code
Clemens Eisserer
linuxhippy at gmail.com
Thu Jul 7 13:29:19 PDT 2011
Hi,
After chatting with Roman about the idea behind AWT's event pump
thread I noticed cacio-web doesn't need a seperate thread, as it
doesn't have to pull events.
Instead it gets the events pushed by the event servlet, which calls
into cacio-web as soon as a client submits events which quite
simplifies things a bit :)
I would be happy if you could review the webrev attached, it contains
the changes to the shared cacio source I've in my local repo.
If you think it should be better solved in another way, I am curious
to hear your suggestions. (especially about messing a bit with
cacio/managed/* internals).
Thanks, Clemens
-------------- next part --------------
A non-text attachment was scrubbed...
Name: webrev.tar.bz2
Type: application/x-bzip2
Size: 19548 bytes
Desc: not available
Url : http://mail.openjdk.java.net/pipermail/caciocavallo-dev/attachments/20110707/035539fe/webrev.tar.bz2
More information about the caciocavallo-dev
mailing list