Hi Ben,
I do a lot of processing like this. I like to use the Execute on server
property for the method doing the processing. The structure is pretty
straightforward:
// EOSmethod ( parameters ) -> text
// first off, check the semaphore
If (Not(Semaphore("specialMethod")))
READ ONLY(*) //
Thanks Chip, this will be helpful! Unfortunately a different project just came
up, so I can't actually start work on the semaphore project until I finish.
- Ben
> my outline for this would be as follows. I am not up to v16 yet, so
> this will be a 'classic' solution, use of call worker might
my outline for this would be as follows. I am not up to v16 yet, so
this will be a 'classic' solution, use of call worker might simplify
this.
write a deamon (a process which spends most of it's life asleep), is
started at server startup.
Deamon :
repeat loop
examine IP array, or
Hello,
Hoping someone can point me in the right direction as I've never done something
like this before.
We have a multi-user environment running v16r5. Through various means, a user
can call a method that updates company-specific financial data. The problem is
that it can take 30+ seconds
4 matches
Mail list logo