Hairy brainstorm

Discussion in 'Python' started by castironpi@gmail.com, Feb 16, 2008.

  1. Guest

    Hold the future holds effectively nothing for single-threaded
    programs; single-core PUs have reached the point of diminishing
    returns of circuit size and IC design; thinking multi-threaded's the
    way to go.

    Recognizing that even in event-driven programs, order of execution is
    important, what does a new thread for each event in a Gui TK look like?
     
    , Feb 16, 2008
    #1
    1. Advertising

  2. Guest

    On Feb 15, 8:04 pm, wrote:
    > Hold the future holds effectively nothing for single-threaded
    > programs; single-core PUs have reached the point of diminishing
    > returns of circuit size and IC design; thinking multi-threaded's the
    > way to go.
    >
    > Recognizing that even in event-driven programs, order of execution is
    > important, what does a new thread for each event in a Gui TK look like?


    Caviat, an OS may design event notifications flows to return values.

    Can an OS, speaking strictly abstractly, spawn a separate thread upon
    an interrupt? ...-tion?
     
    , Feb 16, 2008
    #2
    1. Advertising

  3. Guest

    On Feb 15, 11:43 pm, wrote:
    > On Feb 15, 8:04 pm, wrote:
    >
    > > Hold the future holds effectively nothing for single-threaded
    > > programs; single-core PUs have reached the point of diminishing
    > > returns of circuit size and IC design; thinking multi-threaded's the
    > > way to go.

    >
    > > Recognizing that even in event-driven programs, order of execution is
    > > important, what does a new thread for each event in a Gui TK look like?

    >
    > Caviat, an OS may design event notifications flows to return values.
    >
    > Can an OS, speaking strictly abstractly, spawn a separate thread upon
    > an interrupt?  ...-tion?


    In Windows, events either come from one's main loop:

    while( GetMessage( &arg ) )
    DispatchMessage( &arg );

    (DispatchMessage calls HandlerProc), or are a direct callback /of/
    HandlerProc, registered with the system, by the system. Premise:
    Order is unimportant. Add these APIs:

    while( GetMessage( &arg ) )
    DispatchMessageThdd( &arg );

    Either: DispatchMessageThdd and the system call HandlerProc in "the
    right" thread: an existing one, if the event is in a special sequence,
    or a new one otherwise; Or, they always calls HandlerProc in a new
    thread, and when order is important, one can synchronize.
    Complicated, but distributed.

    Messages can be disserialized in at least one case. Serial APIs
    remain. DispatchMessageThdd raises the performance ceiling in the
    abstract case.
     
    , Feb 19, 2008
    #3
    1. Advertising

Want to reply to this thread or ask your own question?

It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum.
Similar Threads
  1. George Durzi

    Brainstorm with me on this

    George Durzi, Dec 9, 2003, in forum: ASP .Net
    Replies:
    1
    Views:
    323
    Alex Papadimoulis
    Dec 11, 2003
  2. Frederick Gotham

    Brainstorm for compile-time constants

    Frederick Gotham, Jun 25, 2006, in forum: C++
    Replies:
    2
    Views:
    332
    Rolf Magnus
    Jun 25, 2006
  3. Timasmith
    Replies:
    1
    Views:
    668
    Knute Johnson
    Mar 13, 2007
  4. desktop
    Replies:
    6
    Views:
    626
    desktop
    Jun 13, 2007
  5. sclaflin

    Hairy generics question

    sclaflin, Feb 21, 2012, in forum: Java
    Replies:
    29
    Views:
    654
    Arne Vajhøj
    Mar 11, 2012
Loading...

Share This Page