Planning ahead for threads and more interactivity in rev apps

Luis luis at anachreon.co.uk
Mon Nov 12 10:59:16 EST 2007


Hiya,

What about offloading the 'threading' to the database record/file locks?
The database needn't hold the files, just pointers.

I understand the speed issue.

Cheers,

Luis.


On 9 Nov 2007, at 09:36, xavier.bury at clearstream.com wrote:

> Hi Luis,
>
> I thought about that long ago, but decided to use flat files to  
> keep the
> stats and this has worked really
> well over the years. One file per server for 400+ servers.
>
> Also DBs are slower in comparison to a file loading... I'd have to  
> make
> one or more transactions per server where as i load the file into a
> variable and i have all the data there...
>
> keeping it simple... The files repository is centralized in this  
> way...
>
> thanks for the suggestion...
> ---------------------=---------------------
> Xavier Bury
> Clearstream Services
> TNS NT LAN Server
>
>
> use-revolution-bounces at lists.runrev.com wrote on 09/11/2007 10:31:14:
>
>> Instead of files 'per se', why not write to a database? Keeping it
>> centralised.
>>
>> Cheers,
>>
>> Luis.
>>
>>
>> On 9 Nov 2007, at 09:28, xavier.bury at clearstream.com wrote:
>>
>>> Thanks for everyone's input...
>>>
>>> I came to the conclusion that my once-simple scanning program  
>>> ended up
>>> with too many reporting features. So i have to separate them. I
>>> will have
>>> 3 different applications in the end. One for scanning, one for
>>> monitoring
>>> the scanning and one to do the reporting.
>>>
>>> I cannot use sockets or the like just because of the complexity it
>>> would
>>> add to the system plus the lack of tracking should anything go
>>> wrong. This
>>> is the same kind of issues with a cgi-based processes - if any of  
>>> them
>>> hang, you dont know which one it is and you must kill all the
>>> processes to
>>> be clean again... We've had lots of issues with this which is why i
>>> wont
>>> go that way.
>>>
>>> The plan i made is to write simple transactions to files and have a
>>> cmd
>>> helper run these. These create their logs which is what i need and
>>> then
>>> delete the transaction file once done. This way if anything happens
>>> i can
>>> track where it went wrong (the transaction is not deleted for
>>> example)...
>>> Also i can limit the number of processes easily since rev creates  
>>> the
>>> transactions
>>> only if there is no excess transactions left to be done...
>>>
>>> Thanks too all who answered for your help and suggestions!
>>> ---------------------=---------------------
>>> Xavier Bury
>>> Clearstream Services
>>> TNS NT LAN Server
>>>
>>>
>>>
>>> -------------------------------------------------------------------- 
>>> --
>
>>> ------
>>> Clearstream Services S.A.
>>> 42 Avenue JF Kennedy, L-1855 Luxembourg
>>> Société anonyme is organised with limited liability
>>> in the Grand Duchy of Luxembourg R.C.S. Luxembourg B 60911.
>>>
>>>
>>> -----------------------------------------
>>> Visit us at http://www.clearstream.com
>>>
>>> IMPORTANT MESSAGE
>>>
>>> Internet communications are not secure and therefore Clearstream
>>> International does not accept legal responsibility for the contents
>>> of this message.
>>>
>>> The information contained in this e-mail is confidential and may be
>>> legally privileged. It is intended solely for the addressee. If you
>>> are not the intended recipient, any disclosure, copying,
>>> distribution or any action taken or omitted to be taken in reliance
>>> on it, is prohibited and may be unlawful. Any views expressed in
>>> this e-mail are those of the individual sender, except where the
>>> sender specifically states them to be the views of Clearstream
>>> International or of any of its affiliates or subsidiaries.
>>>
>>> Legally required information for business correspondence/
>>> Gesetzliche Pflichtangaben fuer Geschaeftskorrespondenz:
>>> http://deutsche-boerse.com/letterhead
>>>
>>> END OF DISCLAIMER
>>> _______________________________________________
>>> use-revolution mailing list
>>> use-revolution at lists.runrev.com
>>> Please visit this url to subscribe, unsubscribe and manage your
>>> subscription preferences:
>>> http://lists.runrev.com/mailman/listinfo/use-revolution
>>>
>>
>> _______________________________________________
>> use-revolution mailing list
>> use-revolution at lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your
>> subscription preferences:
>> http://lists.runrev.com/mailman/listinfo/use-revolution
>
>
>
> ---------------------------------------------------------------------- 
> ------
> Clearstream Services S.A.
> 42 Avenue JF Kennedy, L-1855 Luxembourg
> Société anonyme is organised with limited liability
> in the Grand Duchy of Luxembourg R.C.S. Luxembourg B 60911.
>
>
> -----------------------------------------
> Visit us at http://www.clearstream.com
>
> IMPORTANT MESSAGE
>
> Internet communications are not secure and therefore Clearstream
> International does not accept legal responsibility for the contents
> of this message.
>
> The information contained in this e-mail is confidential and may be
> legally privileged. It is intended solely for the addressee. If you
> are not the intended recipient, any disclosure, copying,
> distribution or any action taken or omitted to be taken in reliance
> on it, is prohibited and may be unlawful. Any views expressed in
> this e-mail are those of the individual sender, except where the
> sender specifically states them to be the views of Clearstream
> International or of any of its affiliates or subsidiaries.
>
> Legally required information for business correspondence/
> Gesetzliche Pflichtangaben fuer Geschaeftskorrespondenz:
> http://deutsche-boerse.com/letterhead
>
> END OF DISCLAIMER
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your  
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-revolution
>




More information about the Use-livecode mailing list