Like with Artemis, there's the Artemis-native, where I isolate the use of the native module.
Maybe you could create a project to just control MapFiles.. it would be easier to maintain it I think. On Thu, Jun 9, 2016 at 2:20 PM, Clebert Suconic <[email protected]> wrote: > I would isolate it on a library. Netty does have it but it's well > controlled on a single place I think (easier to maintain it) > > I had played with memory mapped years ago and I've decided to use > libaio instead. Did you run any micro benchmarks, have you made any > progress? it seems like a nice idea if you found a breakthrough on > making it performant.. I'm quite interested on it. > > On Wed, Jun 8, 2016 at 10:52 AM, nigro_franz <[email protected]> wrote: >> Hi to everyone! >> >> I've developed a memory mapped implementation of SequenceFile to be used >> inside Artemis's Journal and i've encountered a big question: can i use >> sun.misc.Unsafe? >> >> I've noticed that between all the dependencies of Artemis there was Netty's >> libs with its PlatformDependent class and i've finally choose to use it >> instead of "naked" Unsafe,but i'm not completly satisfied by this solution >> because PlatformDependent does not provide all the methods of Unsafe (e.g. >> Unsafe::pageSize). >> With such methods there are a lot of improvements and features that can be >> developed, considering that in the future of Java there will be a place for >> a safer Unsafe :) >> There exists a good policy for all that cases in which something so "unsafe" >> and "platform dependend" is needed?What the other devs think about it? >> >> >> With Regards, >> Francesco >> >> >> >> >> >> -- >> View this message in context: >> http://activemq.2283324.n4.nabble.com/sun-misc-Unsafe-VS-io-netty-util-internal-PlatformDependent-VS-null-tp4712785.html >> Sent from the ActiveMQ - Dev mailing list archive at Nabble.com. > > > > -- > Clebert Suconic -- Clebert Suconic
