Closed GoogleCodeExporter closed 9 years ago
[ThreadStatic]
private static Property<T>[] readProps, writeProps;
[ThreadStatic]
private static KeyValuePair<Type, Property<T, T>>[] subclasses;
Original comment by kiminozo...@gmail.com
on 9 Dec 2008 at 2:04
OK, I will post a fix later today - but I don't think [ThreadStatic] will be
the way,
since that would preclude any re-use. It will be something related, though.
Original comment by marc.gravell
on 9 Dec 2008 at 4:58
I wait for to hear your good news.
Original comment by kiminozo...@gmail.com
on 9 Dec 2008 at 5:48
Original comment by marc.gravell
on 9 Dec 2008 at 8:35
(fixed in latest build)
Original comment by marc.gravell
on 9 Dec 2008 at 10:19
Oh,I have seen the latest build;
I find there is a new object "lockToken" to lock the threaded-unsafe-process.
but I don't think the Monitor will be the way,
the Monitor just make a multi-thread program to a one-thread program.
I think it is not highly active way.
Original comment by kiminozo...@gmail.com
on 9 Dec 2008 at 12:42
No, that isn't what it does... the lock is *only* taken during the Build()
step; and
only if the model hasn't already been built. For most cases, this will mean
only one
use of lock per-type, and after that no locks at all.
This change does not serialize calls to the main serialization code.
Original comment by marc.gravell
on 9 Dec 2008 at 1:39
Ah, that accounts for it!
I will try it again tomorrow.
Original comment by kiminozo...@gmail.com
on 9 Dec 2008 at 2:15
Oh, I have tested again . You are right.
Original comment by kiminozo...@gmail.com
on 10 Dec 2008 at 3:03
Closed (verified)
Original comment by marc.gravell
on 6 Jan 2009 at 7:51
Original issue reported on code.google.com by
kiminozo...@gmail.com
on 9 Dec 2008 at 1:54Attachments: