Changeset 197

Show
Ignore:
Timestamp:
11/13/07 20:58:36 (1 year ago)
Author:
gethema..@gmail.com
Message:

send the README

Files:

Legend:

Unmodified
Added
Removed
Modified
Copied
Moved

  • branches/version10/README

    r196 r197  
    2828  svn up vendor/plugins 
    2929  rake backgroundrb:setup 
    30  
    3130 
    3231Installation with piston: 
    …… 
    106105  'create' method gets called, when worker is loaded and created. Each worker runs in its 
    107106  own process and you can use 'create' for initializing worker specific stuff. 
    108   All the requests, send from rails, to bdrb would be received in process_request method. 
     107  All the requests, sent from rails, to bdrb would be received in process_request method. 
    109108  Received data, contains client address as well, which will be used to send the response 
    110109  back to client. You just need to extract the data from received data and call appropriate 
    …… 
    118117  arguments '10+10' and return the result. 
    119118 
    120     p MiddleMan.send_request(:worker => :foo_worker, :method => :add_values,:data => "10+10") 
     119      MiddleMan.send_request(:worker => :foo_worker, :method => :add_values,:data => "10+10") 
    121120 
    122121  You can also use register_status as described in following snippet to register status of 
    …… 
    137136=== Legacy and deprecated stuff 
    138137 
    139    Although, You need to wrap your head a bit for understanding "evented" model of network programming a bit, 
    140    but it gets easier once you get the hang of it. Much of the older stuff is deprecated. Here is a brief list: 
     138   Although, You need to wrap your head a bit for understanding "evented" model of network programming, 
     139   but it gets easier once you get hang of it. Much of the older stuff is deprecated. Here is a brief list: 
    141140 
    142141   - ACL : gone, trust to thy firewalls. 
    …… 
    171170 
    172171=== Exciting new stuff 
    173   * Rock solid stable. 
    174   * Master is using a hash for storing status of each worker. I am thinking of adding something like this: 
     172  * Rock solid stable ( or will be , after few bug reports ) 
     173  * Master Process is using a hash for storing status of each worker. I am thinking of adding something like this: 
    175174 
    176175        #backgroundrb.yml 
    …… 
    178177          storage: db 
    179178          database: worker_status 
     179    Above code would fullfill thy wishes of persitent worker status storage. Any more ideas, welcome. 
    180180  * Each worker comes with Event loop of its own and can potentially do lots of fancy stuff. Two noteworthy methods are: 
    181181