OpenEuphoria

RE: Threads?

• Posted by Andy Serpa <renegade at earthling.net> Oct 10, 2002
• 378 views

Kat wrote:
> On 10 Oct 2002, at 7:30, Andy Serpa wrote:
> 
> > 
> > jbrown105 at speedymail.org wrote:
> > > On  0, Kat <kat at kogeijin.com> wrote:
> > > > 
> > > > On 9 Oct 2002, at 22:56, Robert Craig wrote:
> > > > 
> > > > > 
> > > > > Kat writes:
> > > > > > Other than socks or dde, is there 
> > > > > > any way to signal the other process(es) that there is work to be
> > > > > > done?
> > > > > 
> > > > > Have a look at Jordah Ferguson's demo where 
> > > > > processes pass Euphoria data to each other via shared memory.
> > > > > He uses a library developed by Mario Steele and Jason Mirwald.
> > > > > I think jbrown was doing something similar on Linux.
> > > > > A process could sleep() and periodically check a value in 
> > > > > shared memory.
> > > > 
> > > > Sleep()ing isn't the same as an event trigger.
> > > > 
> > > > Kat
> > > > 
> > > 
> > > No, but it comes close to emulating it.
> > > 
> > > Under *nix, you can also use signals as triggers, signals + shared 
> > > memory
> > > should od the trick: the signal can be the event trigger and the shared 
> > > mem
> > > can transfer the variable states shared between processes. (This is what 
> > > I
> > > tried to do, but I was unable to solve the race condition which tended 
> > > to
> > > corrupt the database. File locks and mutexes both failed for me, hence I
> > > resorted to socks.)
> > > 
> > > Is there any similar mechanism to signals under Win32? You could use 
> > > that
> > > as the event trigger.
> > > 
> > > jbrown
> > > 
> > > 
> > See my post "Fun with doEvents()" a couple dozen back -- that is a quick 
> > 
> > & dirty way to run multiple procedures under win32lib...
> 
> That's all done in one application, i mean between separate Eu 
> applications. 
> What about the Eu code that presses buttons in other apps, can it 
> trigger an 
> on_whatever event in any other Eu application?
> 
> 

Beats me, but here is somthing David Cuny said a couple of months ago 
here:

-----------------
Any Windows program can send events to another Windows program. This has 
been 
shown to be the basis for some interesting security holes. For example, 
people have written programs send messages to shareware programs to 
activate 
dimmed buttons. An insecurity was published last week that increased the 

allowable size of a sent code to a trusted application's edit box (in 
this 
case, a virus scanner) and then told it to execute it at root level.
---------------------