Re: [v8-users] BSON to v8::Object performance issue

2017-11-16 Thread J Decker
You don't manage the instance, the v8 engine does. When it's no longer referenced in the engine, it's garbage collected which triggers the callback set when the perisstent object is made weak. You don't need to keep it anywhere, the object returned into the engine has Internal Fields ( SetInterna

Re: [v8-users] BSON to v8::Object performance issue

2017-11-16 Thread Jean-Marc Le Roux
> > Node offers a C++ Clss extention ObjectWrap Thanks ! It is related to node. Yet I'm not sure how I'm supposed to use ObjectWrap. I understand I have to create my own class that extends ObjectWrap and implement a proper destructor. Then I'll instanciate that class to wrap my Local. But how do

Re: [v8-users] BSON to v8::Object performance issue

2017-11-16 Thread J Decker
On Thu, Nov 16, 2017 at 1:24 AM, Jean-Marc Le Roux wrote: > I assume you're storing references to the objects as Persistent? > > > Nope. You've got the whole code up there. > So if I understand correctly: > >- the objects I need to keep track of the lifecycle should be made >Persistent ;

Re: [v8-users] BSON to v8::Object performance issue

2017-11-16 Thread Jean-Marc Le Roux
> > I assume you're storing references to the objects as Persistent? Nope. You've got the whole code up there. So if I understand correctly: - the objects I need to keep track of the lifecycle should be made Persistent ; - all the other values can be set as Local ; - I should set the