Source language: Translate to:

New npFile NeoPlugin for NeoBook

Questions about NeoBook PlugIns

Moderator: Neosoft Support

New npFile NeoPlugin for NeoBook

Postby dec » Mon Jan 23, 2012 3:19 pm

Hi to all!

This plugin allow you to work with files in an advanced mode, allowing, for example, to open share exclusive files, which can be only read or write from your publication and not for others while the file are in use.

You can create the File objects instances that you need. Every File instance allow you to create, read and write files, in a share exclusive mode or others. The plugin allow you to read or write the files byte by byte and more.

You can download the npFile from here.

Thank you!
Last edited by dec on Fri Mar 09, 2012 4:20 am, edited 1 time in total.
.
Enhance your NeoBook applications!
.
57 plugins, 1113 actions and 230 samples
.
NeoPlugins website: www.neoplugins.com
.
User avatar
dec
 
Posts: 1663
Joined: Wed Nov 16, 2005 12:48 am
Location: Spain

Postby cp4w » Wed Jan 25, 2012 9:55 am

Hi David,

What would happen if pub locked (Open share exclusive) a file via your plug-in and for some reason the pub crashed or the computer was turned of before the pub could release the lock? Would the lock automatically be freed?
cp4w
 
Posts: 533
Joined: Sun Apr 03, 2005 4:37 pm
Location: Great Neck, NY

Postby dec » Wed Jan 25, 2012 10:04 am

Hi Steven,

shx wrote:Hi David,

What would happen if pub locked (Open share exclusive) a file via your plug-in and for some reason the pub crashed or the computer was turned of before the pub could release the lock? Would the lock automatically be freed?


I think so, since when something like this happend the memory is released, the handle which "lock" the file is also released. For example, when you create a File object instance, you can free it after use it (as a good thing), but, if you not doing this, when the publication is closed the file is released in any case.

I think in the case that the publication still in memory... but in a case like this, we need try to solve this problem: we never permit that a publication which is closed remain executing in memory. So we need to found the possible problem that cause this behaviour and fix it.

In any other cases, suposing the publication, sometime, without any reason (...), crash and remain in memory... well, since this is not the normal behaviour, we can't expect act like that. Sometimes happend this things and we (as users) need to terminate the application process, for example: when doing this the file handle (if any) is released.
.
Enhance your NeoBook applications!
.
57 plugins, 1113 actions and 230 samples
.
NeoPlugins website: www.neoplugins.com
.
User avatar
dec
 
Posts: 1663
Joined: Wed Nov 16, 2005 12:48 am
Location: Spain


Return to PlugIn Discussions

Who is online

Users browsing this forum: No registered users and 2 guests

cron