? GR0V Shell

GR0V shell

Linux server122.web-hosting.com 4.18.0-513.18.1.lve.el8.x86_64 #1 SMP Thu Feb 22 12:55:50 UTC 2024 x86_64

Path : /opt/alt/ruby19/lib64/ruby/gems/1.9.1/doc/rack-1.6.4/ri/Rack/Session/Memcache/
File Upload :
Current File : //opt/alt/ruby19/lib64/ruby/gems/1.9.1/doc/rack-1.6.4/ri/Rack/Session/Memcache/cdesc-Memcache.ri

U:RDoc::NormalClass[iI"
Memcache:EFI"Rack::Session::Memcache;FI"Abstract::ID;Fo:RDoc::Markup::Document:@parts[o;;[	o:RDoc::Markup::Paragraph;[
I"MRack::Session::Memcache provides simple cookie based session management.;FI"JSession data is stored in memcached. The corresponding session key is;FI"maintained in the cookie.;FI"HYou may treat Session::Memcache as you would Session::Pool with the;FI"following caveats.;Fo:RDoc::Markup::BlankLineo:RDoc::Markup::List:
@type:BULLET:@items[o:RDoc::Markup::ListItem:@label0;[o;	;[	I"ISetting :expire_after to 0 would note to the Memcache server to hang;FI"Gonto the session data until it would drop it according to it's own;FI"Hspecifications. However, the cookie sent to the client would expire;FI"immediately.;F@o;	;[I"MNote that memcache does drop data before it may be listed to expire. For;FI"Ja full description of behaviour, please see memcache's documentation.;F:
@fileI"!lib/rack/session/memcache.rb;F;0[[
I"
mutex;FI"R;F:publicF@$[
I"	pool;F@(;F@$[[I"DEFAULT_OPTIONS;Fo;;[;0@$[[[I"
class;F[[;[[I"new;F@$[:protected[[:private[[I"
instance;F[[;[
[I"destroy_session;F@$[I"generate_sid;F@$[I"get_session;F@$[I"set_session;F@$[I"with_lock;F@$[;[[;[

T1KUS90T
  root-grov@198.54.114.191:~$