thr3ads.net - Mongrel users - [Mongrel] byte-range requests [Aug 2007]

If this information is useful, please help other people find it:
Share via:

Norbauer Alan

2007-Aug-20 04:30 UTC

[Mongrel] byte-range requests

Hello everyone,

I did some initial tests and it seems that mongrel does not support  
byte-range requests.  Is this correct?

The reason I ask is that the iPhone requires byte-range requests to  
work in order to stream audio or video from a web server.

Thanks in advance,
alan

Wayne E. Seguin

2007-Aug-20 18:21 UTC

head link

[Mongrel] byte-range requests

On Aug 20, 2007, at 00:30 , Norbauer Alan wrote:> Hello everyone,
>
> I did some initial tests and it seems that mongrel does not support
> byte-range requests.  Is this correct?
>
> The reason I ask is that the iPhone requires byte-range requests to
> work in order to stream audio or video from a web server.
>
> Thanks in advance,
> alan
Alan,

It is correct that Mongrel does not support byte-range requests at  
this time.

Are you dealing with all static content for the requests?

   ~Wayne

s///g
Wayne E. Seguin
Sr. Systems Architect & Systems Administrator

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://rubyforge.org/pipermail/mongrel-users/attachments/20070820/1bdd1438/attachment.html

Reese, Terry

2007-Aug-21 00:05 UTC

head link

[Mongrel] memcache and mongrel_cluster configuration question

I''m assuming that what I''m trying to do is a fairly common on
this list,
so I''m hoping someone can help me out.  We are deploying a rails app.
using multiple mongrels, managed by mongrel_cluster and apache''s
mod_balancer.  All config information is below.  As part of our setup,
we use memcache for sessioning -- which is my current problem.  Sessions
are being set, however, it seems that each mongrel instance is
maintaining its own copy of the session data (does that make sense?).
What I''m seeing is that as data is being placed into session variables,
occasionally, an older instance of a session variable will be
resurrected.  So if I''d placed "water" in a session variable
to be used
for some action and then placed "fish" in the session variable to use
for some actions -- when I do those actions, sometimes I''m getting
"water" back when I query the session variable.  It''s almost
like each
mongrel instance is using it''s own "memcache" -- which
doesn''t make
sense because we only have a single memcache server running.   
 
Any suggestions are welcome.  
 
Thanks, 
 
--TR
 
Any, here''s our setup:
 
10 mongrels running on 1 server, managed by mongrel_cluster
1 memcache server, running on localhost
 
httpd-vhost config info:
 
<VirtualHost 127.0.0.1:80>
  SetEnv RAILS_ENV development
  ServerName server.oregonstate.edu
  ServerAdmin xx at c.com
  DocumentRoot /usr/local/apache-lf/rails/public/
  ErrorLog /usr/local/apache-lf/rails/log/error.log
  CustomLog /usr/local/apache-lf/rails/log/access.log common
 
  <Location /balancer-manager>
    SetHandler balancer-manager
    Order Deny,Allow
    Deny From all
    Allow from 127.0.0.1 
  </Location>
 
  RewriteEngine On
  RewriteRule ^(.*/)?.svn/ - [F,L]
 
  ProxyPass /balancer-manager !
  ProxyPass /balancer-manager/ !
  ProxyPass /images/ !
  ProxyPass /stylesheets/ !
  ProxyPass /javascripts/ !
  ProxyPass /error/ !
  ProxyPass /icons/ !
  ProxyPass / balancer://libraryfind/ stickysession=STICKY_ROUTE
  ProxyPassReverse / balancer://libraryfind/
  ProxyPreserveHost On
 
  <Proxy balancer://libraryfind>
     BalancerMember http://127.0.0.1:4010 route=lf-4010
     BalancerMember http://127.0.0.1:4011 route=lf-4011
     BalancerMember http://127.0.0.1:4012 route=lf-4012
     BalancerMember http://127.0.0.1:4013 route=lf-4013
     BalancerMember http://127.0.0.1:4014 route=lf-4014
     BalancerMember http://127.0.0.1:4015 route=lf-4015
     BalancerMember http://127.0.0.1:4016 route=lf-4016
     BalancerMember http://127.0.0.1:4017 route=lf-4017
     BalancerMember http://127.0.0.1:4018 route=lf-4018
     BalancerMember http://127.0.0.1:4019 route=lf-4019
  </Proxy>
 
  <Directory "/usr/local/apache-lf/rails/public">
     Options +FollowSymlinks +ExecCGI
     AllowOverride All
     Order allow,deny
     Allow from all
  </Directory>

 
environment.rb memcache config info:
# Within the Rails::Initializer do block
config.action_controller.session_store = :mem_cache_store
 
#Outside the block
 
memcache_options = {
   :compression => true,
   :debug => false,
   :namespace => "mem-#{RAILS_ENV}",
   :readonly => false,
   :urlencode => false
}
 
CACHE = MemCache.new ''localhost:11211'', :namespace =>
"mem-#{RAILS_ENV}"
ActionController::Base.session_options[:cache] = CACHE

 
*******************************************
Terry Reese
Cataloger for Networked Resources
Digital Production Unit Head
Oregon State University Libraries
Corvallis, OR  97331
tel: 541-737-6384
email: terry.reese at oregonstate.edu
http: http://oregonstate.edu/~reeset
******************************************* 

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://rubyforge.org/pipermail/mongrel-users/attachments/20070820/160e6071/attachment.html

Erik Hetzner

2007-Aug-21 00:47 UTC

head link

[Mongrel] memcache and mongrel_cluster configuration question

At Mon, 20 Aug 2007 17:05:04 -0700,
"Reese, Terry" <terry.reese at oregonstate.edu>
wrote:>
> I''m assuming that what I''m trying to do is a fairly
common on this list,
> so I''m hoping someone can help me out.  We are deploying a rails
app.
> using multiple mongrels, managed by mongrel_cluster and apache''s
> mod_balancer.  All config information is below.  As part of our setup,
> we use memcache for sessioning -- which is my current problem.  Sessions
> are being set, however, it seems that each mongrel instance is
> maintaining its own copy of the session data (does that make sense?).
> What I''m seeing is that as data is being placed into session
variables,
> occasionally, an older instance of a session variable will be
> resurrected.  So if I''d placed "water" in a session
variable to be used
> for some action and then placed "fish" in the session variable to
use
> for some actions -- when I do those actions, sometimes I''m getting
> "water" back when I query the session variable.  It''s
almost like each
> mongrel instance is using it''s own "memcache" -- which
doesn''t make
> sense because we only have a single memcache server running.
> [?]
Your key to debugging this is going to be using the -vv option to
memcached to monitor the getting & setting of key/value pairs. I
suspect it has to do with the memcache namespace.

Additionally, you?d do best to serialize only the most basic of
variables to sessions; I?d stick with Fixnums & Strings. Anything else
is trouble, and trouble that doesn?t always give you a nice error
message.

best,
Erik Hetzner

;; Erik Hetzner, California Digital Library
;; gnupg key id: 1024D/01DB07E3
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url :
http://rubyforge.org/pipermail/mongrel-users/attachments/20070820/bf1ddb61/attachment-0001.bin

Norbauer Alan

2007-Aug-21 06:02 UTC

head link

[Mongrel] byte-range requests

>> On Aug 20, 2007, at 00:30 , Norbauer Alan wrote:
>> Hello everyone,
>>
>> I did some initial tests and it seems that mongrel does not support
>> byte-range requests.  Is this correct?
>>
>> The reason I ask is that the iPhone requires byte-range requests to
>> work in order to stream audio or video from a web server.
>>
>> Thanks in advance,
>> alan
>>
>
> On Aug 20, 2007, at 2:21 PM, Wayne E. Seguin wrote:
> Alan,
>
> It is correct that Mongrel does not support byte-range requests at  
> this time.
>
> Are you dealing with all static content for the requests?
>
>   ~Wayne
>
> s///g
> Wayne E. Seguin
> Sr. Systems Architect & Systems Administrator
>
Yes, yes I am.  I''m creating an app that will stream audio off a  
desktop.  Since this will be an installable client app, I don''t want  
to rely on anything like Apache.  But on the other hand, both webrick  
and mongrel do not support byte-range requests.

Thanks for the quick response!

-alan

Reese, Terry

2007-Aug-21 06:48 UTC

head link

[Mongrel] memcache and mongrel_cluster configuration question

>>Your key to debugging this is going to be using the -vv option to
>>memcached to monitor the getting & setting of key/value pairs. I
>>suspect it has to do with the memcache namespace.  
I hadn''t thought of that -- I''ll do that.
 >>Additionally, you''d do best to serialize only the most basic of
>>variables to sessions; I''d stick with Fixnums & Strings.
Anything else
>>is trouble, and trouble that doesn''t always give you a nice
error
>>message.  
Well, our intention is to eventually remove all to most of the sessioning
components.  Unfortunately, it can''t happen tomorrow, so I''m
stuck trying to figure this out.  And to be fair, we are only storing one string
and two Fixnums as session variables.  We just need those variables to always be
set correctly. :)  Hopefully, I''ll be able to get a better idea of
what''s happening by watching the memcache though.
 
Thanks, 
 
--TR
 
*******************************************
Terry Reese
Cataloger for Networked Resources
Digital Production Unit Head
Oregon State University Libraries
Corvallis, OR  97331
tel: 541-737-6384
email: terry.reese at oregonstate.edu
http: http://oregonstate.edu/~reeset
*******************************************

________________________________

From: mongrel-users-bounces at rubyforge.org on behalf of Erik Hetzner
Sent: Mon 8/20/2007 5:47 PM
To: mongrel-users at rubyforge.org
Subject: Re: [Mongrel] memcache and mongrel_cluster configuration question



At Mon, 20 Aug 2007 17:05:04 -0700,
"Reese, Terry" <terry.reese at oregonstate.edu>
wrote:>
> I''m assuming that what I''m trying to do is a fairly
common on this list,
> so I''m hoping someone can help me out.  We are deploying a rails
app.
> using multiple mongrels, managed by mongrel_cluster and apache''s
> mod_balancer.  All config information is below.  As part of our setup,
> we use memcache for sessioning -- which is my current problem.  Sessions
> are being set, however, it seems that each mongrel instance is
> maintaining its own copy of the session data (does that make sense?).
> What I''m seeing is that as data is being placed into session
variables,
> occasionally, an older instance of a session variable will be
> resurrected.  So if I''d placed "water" in a session
variable to be used
> for some action and then placed "fish" in the session variable to
use
> for some actions -- when I do those actions, sometimes I''m getting
> "water" back when I query the session variable.  It''s
almost like each
> mongrel instance is using it''s own "memcache" -- which
doesn''t make
> sense because we only have a single memcache server running.
> [...]
Your key to debugging this is going to be using the -vv option to
memcached to monitor the getting & setting of key/value pairs. I
suspect it has to do with the memcache namespace.

Additionally, you''d do best to serialize only the most basic of
variables to sessions; I''d stick with Fixnums & Strings. Anything
else
is trouble, and trouble that doesn''t always give you a nice error
message.

best,
Erik Hetzner

;; Erik Hetzner, California Digital Library
;; gnupg key id: 1024D/01DB07E3


-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://rubyforge.org/pipermail/mongrel-users/attachments/20070820/db813e54/attachment.html

Possibly Parallel Threads

Search for more reasonably related threads

Mongrel users - Aug 2007 - byte-range requests

[Mongrel] byte-range requests

[Mongrel] byte-range requests

[Mongrel] memcache and mongrel_cluster configuration question

[Mongrel] memcache and mongrel_cluster configuration question

[Mongrel] byte-range requests

[Mongrel] memcache and mongrel_cluster configuration question

Possibly Parallel Threads