Re: windows multithreading update to TDLL and APC_DLL

new topic     » goto parent     » topic index » view thread      » older message » newer message

c.k.lester wrote:
> 
> Daniel Kluss wrote:
> > c.k.lester wrote:
> > > Daniel Kluss wrote:
> > > > you can now call blocking dll/asm calls from seperate euphoria threads
> > > > and have no polling overhead, try it.
> > > > temporary url
> > > > <a
> > > > href="http://www.rapideuphoria.com/uploads/sdll.zip">http://www.rapideuphoria.com/uploads/sdll.zip</a>
> > > AWESOME!!!!!!
> > > (Uh, what does that mean? :D)
> > It means that now you can code like your really doing multiple threads, and
> > call blocking
> > windows/c/dll/assembly calls and only the 1 euphoria thread that called it
> > waits,
> > while the
> > other ones continue doing there own thing.
> 
> That certainly sounds important. What are some examples of dlls that are
> blocking and examples that are non-blocking? I'm guessing something like
> file access would be blocking and grabbing a file off the internet would
> be non-blocking.

Thats it, most winsock, file and all sorts of other stuff is blocking.
But, even more so, there are many libraries full of functions that, are blocking
but not signaled so the only way to do more than 1 at a time is with threading
and still other functions don't just wait while they block, but actually do
stuff.
for example, compressing a file, you just call some dll, and you have to wait
till it's done,
but now you call my stuff and you can do a 1000 at the same time.

Daniel

new topic     » goto parent     » topic index » view thread      » older message » newer message

Search



Quick Links

User menu

Not signed in.

Misc Menu