Someone on stackoverflow suggested using rainbows instead of juggernaut/node.js for sending push notifications via comet. But I can't seem to find anything about setting something up like that. Thanks. _______________________________________________ Rainbows! mailing list - rainbows-talk@... http://rubyforge.org/mailman/listinfo/rainbows-talk Do not quote signatures (like this one) or top post when replying
Laba diena, Rašome Jums iš įmonės „Internet Solutions“. Norime informuoti, kad kuriame interneto svetaines (nemokamai), klientai moka tik už svetainės talpinimą mūsų serveryje. Atsinaujinusius svetainių talpinimo planus ir įkainius rasite pateiktoje nuorodoje: http://internetsolutions.lt/tinklapiu-kurimas Galime susikurti svetainę ir be talpinimo paslaugos, dėl kainų teirautis nurodytais kontaktais. Jei jau turite svetainę, galime pasiūlyti svetainės optimizaciją (SEO paslaugas). Plačiau apie tai galite rasti mūsų tinklapyje: http://internetsolutions.lt/reklama-internete/seo-paslaugos/ Taip pat galime pasiūlyti naujienlaiškių siuntimo paslaugas: http://internetsolutions.lt/e-marketingas/naujienlaiskiu-siuntimas/ Geros dienos, -- Evelina Navickaitė UAB „Internet Solutions“ verslo klientų vadybininkė +370 662 35133 sales <at> internetsolutions.lt www.internetsolutions.lt Reg. adresas: Tvenkinių g. 8A, Šakių k., Kauno r. sav. Biuro - korespondencijos adresas: Lyros g. 5, Šiauliai(Continue reading)
Sveiki, Prieš keletą savaičių rašėme Jums dėl interneto svetainių kūrimo ir atnaujinimo. Taigi norėtume dar kartą pasidomėti, galbūt persigalvojote? Įmonės gimtadienio proga visiems užsisakantiems 24 mėnesių svetainės talpinimo paslaugą, taikome 3 mėnesių talpinimo nuolaidą, o visoms kitoms paslaugoms suteikiame 10% nuolaidą (SEO paslaugoms, reklamai internete, naujienlaiškių siuntimui). Nuolaidos taikomos iki 2012 m. gegužės 01 d. Visi mūsų svetainių darbų pvz: http://internetsolutions.lt/tinklapiu-kurimas/keletas-paskutiniu-darbu Talpinimo įkainius rasite čia: http://internetsolutions.lt/tinklapiu-kurimas Naujienlaiškių darbų pvz: http://internetsolutions.lt/e-marketingas/keletas-naujienlaiskiu-pavydziu -- Evelina Navickaitė UAB „Internet Solutions“ verslo klientų vadybininkė +370 662 35133 sales <at> internetsolutions.lt www.internetsolutions.lt Reg. adresas: Tvenkinių g. 8A, Šakių k., Kauno r. sav. Biuro - korespondencijos adresas: Lyros g. 5, Šiauliai(Continue reading)
Hi, please CC me as i am not on the list. i am using rainbows (configured with eventmachine) to serve faye websocket connections. see https://github.com/faye/faye-websocket-ruby. when the first user connects (using websocket protocol), cpu usage goes to 100% and stays there. even when the user is idle or disconnects. is this normal behavior? i inspected the process using dtrace under mac os x and saw that the process is doing a lot of read and write system calls all the time. i can observe the same 100% cpu behavior on linux. so this is not a mac os x issue. here is my config file and command line: # rainbows.conf Rainbows! do use :EventMachine end rainbows config.ru -c path/to/rainbows.conf -E production -p 9292 regards, Lion Vollnhals _______________________________________________ Rainbows! mailing list - rainbows-talk@... http://rubyforge.org/mailman/listinfo/rainbows-talk(Continue reading)
Damian Janowski <jano@...> wrote: > Hello everyone, > > I'm needing to perform a couple of tasks outside of the request cycle. > For instance, I want to ping a web service every X minutes so that I > can maintain a persistent connection to it and have better response > times for some requests that I have to do *inside* the request cycle. > > What would be the reasonable way of doing this? For Raindrops::Watcher, I start a background thread on the first request: git clone git://bogomips.org/raindrops.git $EDITOR lib/raindrops/watcher.rb If you look at the `call' method in raindrops/watcher.rb, the important line is this: # @start is a Mutex and @thr is nil in the initialize method. @start.synchronize { @thr ||= aggregator_thread(env["rack.logger"]) } I avoid starting the background thread at initialization because it'll die on fork (meaning I'd have to recheck it all the time, anyways). The overhead of Mutex#synchronize and @thr||= assignment is negligible in most apps. > I'm thinking the OOB GC is just another example. But the current way > the OOB GC is written makes one think it's a very specific case and(Continue reading)
Hello everyone, I'm needing to perform a couple of tasks outside of the request cycle. For instance, I want to ping a web service every X minutes so that I can maintain a persistent connection to it and have better response times for some requests that I have to do *inside* the request cycle. What would be the reasonable way of doing this? I'm thinking the OOB GC is just another example. But the current way the OOB GC is written makes one think it's a very specific case and not something one should use for other purposes. Thoughts? Thanks in advance. D. _______________________________________________ Rainbows! mailing list - rainbows-talk@... http://rubyforge.org/mailman/listinfo/rainbows-talk Do not quote signatures (like this one) or top post when replying
Hi!
Short introduction: I am working on a simple "one-click" file
sharing web application specific focus on protecting users' privacy [1].
Thanks to Rainbows! it can work with big uploads without any request
buffering which is simply marvelous! :)
I am currently trying to implement a limit on the maximum uploaded file
size, not unlike what is already done by Rainbows::MaxBody.
Unfortunately, it looks like answering a request while the client is in
the middle of posting data is not supported that well by Rainbows!
Here is a minimal test case:
--- 8< --- config.ru ---------------------------------------------------
class InterruptTest
def call(env)
# HTTP 1.1 standard (and curl) needs this
/\A100-continue\z/i =~ env['HTTP_EXPECT'] and return [ 100, {}, [] ]
error = "Request entity too large!\n"
env['rack.input'].read 1000
Rainbows.sleep 1
[ 403, { 'Content-Type' => 'text/plain' }, [ error ] ]
end
end
run InterruptTest.new
(Continue reading)http://www.zarlav.net Монголын интернет 40 зарын сайтын нэг цэгийн үйлчилгээ 1. Зарын 40 сайтаас зараа хайх болон өгөхөд /үнэгүй/ 2. Гадаад болон Монгол кинонууд үзэх /үнэгүй/ 3. 10.000 ширхэг тоглоомоос сонгон тоглох /үнэгүй/ 4. Арван хурууны бичээч програм татах /үнэгүй/ --------------------------------------------------- Та иймэрхүү байдлаар 200.000 хэрэглэгчдэд И-Мэйл сурталчилгаа хийлгэхэд 300.000 төг холбоо барих : advertise_mon <at> yahoo.com _______________________________________________ Rainbows! mailing list - rainbows-talk <at> rubyforge.org http://rubyforge.org/mailman/listinfo/rainbows-talk Do not quote signatures (like this one) or top post when replying
Hello Rainbows, I was trying to `use :CoolioFiberSpawn` with `Rainbows.sleep` to simulate asynchrony HTTP requests. However, I keep seeing weird "app error: uninitialized fiber (FiberError)". I spent a few hours (ouch) tracking down to a simple case. Suppose I have a Rack app which has `Rainbows.sleep` inside a each block: https://gist.github.com/1536857 (I am running Ruby 1.9.3) class Weird def call env=nil [1].each{ # if you comment out the each block, then it works Rainbows.sleep 2 } [200, {}, ["ok\n"]] end end Then `run Weird.new` would always cause app error: uninitialized fiber (FiberError) But if I took out the each block inside Weird#call, such like: class Weird def call env=nil Rainbows.sleep 2(Continue reading)
I'm trying to run a Rails app that utilizes HTTP streaming with Rainbows! behind Nginx. Here is my nginx.conf:https://gist.github.com/a749361acd09b6ae80e2 Despite setting proxy_buffering off; it appears that nginx is still buffering the output because I do not get a streaming response. When I curl the app directly (port 3000) I get a proper streaming response, but when I curl nginx (which proxies to the Rails app) I do not get a streaming response. Any thoughts? Thanks,Danny _______________________________________________ Rainbows! mailing list - rainbows-talk@... http://rubyforge.org/mailman/listinfo/rainbows-talk Do not quote signatures (like this one) or top post when replying
* http://zbatery.bogomip.org/ * rainbows-talk@... * git://bogomips.org/zbatery.git * http://zbatery.bogomip.org/NEWS.atom.xml Changes: There are two bugfixes in this release. Rack applications that use fork() internally should now behave as-expected when receiving SIGCHLD. The pid file is also unlinked during a graceful shutdown. Thanks to Damian Janowski for the bug report and confirming the fix! _______________________________________________ Rainbows! mailing list - rainbows-talk@... http://rubyforge.org/mailman/listinfo/rainbows-talk Do not quote signatures (like this one) or top post when replying
RSS Feed4 | |
|---|---|
10 | |
3 | |
6 | |
1 | |
16 | |
7 | |
8 | |
1 | |
19 | |
16 | |
16 | |
3 | |
8 | |
17 | |
27 | |
15 | |
4 | |
13 | |
10 | |
20 | |
8 | |
4 | |
5 | |
4 | |
2 | |
2 | |
31 | |
10 | |
13 |
