On 20 May 2012, at 17:59, Vivian Meazza <vivian.mea...@lineone.net> wrote:
>
> "The current implementation is a simple mark/sweep collector, which should
> be acceptable for most applications. Future enhancements will include a
> "return early" capability for latency-critical applications. The collector
> can be instructed to return after a certain maximum delay, and be restarted
> later. Fancy items like generational collectors fail the "small and simple"
> criteria and are not likely to be
This is interesting - as far as I know, the current GC does not include a
maximum delay and restart facility. If it did, that would entirely satisfy the
current issues. At least by my understanding.
Equally, I've looked at the current GC code and didn't notice any code to
support this feature. Does anyone else have any further information about this?
Since it would be far simpler and more robust than any other solution thus
suggested.
Regards,
James
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
