Re: Camping's URL mapping system
rack has a minimal file-server [0] 0. https://github.com/rack/rack/blob/6496241b25daa20fd9dd736119dc39bdac54869d/lib/rack/file.rb#L70 ive been usin it on my phone to do the basics, it kind of chokes on 128M podcasts as a mediaplayer http://repo.or.cz/w/element.git/blob_plain/HEAD:/doc/find.html it gets the job done though ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
Re: Advice on strategy for maintaining state in Camping
a SQLlight database seems like the best way to go given your initial scenario of read-only Excel files, i disagree. why plumb data from Excel into SQLite and from SQLite into a web UI via several layers of Ruby code, themselves distanced from underlying datastores via ORM libraries, when you can specialized .XLS oriented tools oriented to non-coder (or quasi-coder) i dont have anything to do with Cambridge Semantics, but if i had a copy of Excel or Windows i'd check it.. http://www.cambridgesemantics.com/products/anzo_for_excel if massaging the data or filtering it one could try Refine: https://code.google.com/p/google-refine/ if it was me, i usually use xls2txt and an on-the-fly RDF (to JSON/Hash in RAM) conversion and skip the SQL or non-programmer tools which mean well but never do quite what you want (or require excessive gymnastics vs a few lines of Ruby/Haskell) http://gitorious.org/element/element/blobs/master/ruby/W/csv.rb also Camping may be *just* what you are looking for.. ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
Re: PUT (and friends) bug?
The @method == post test is a vestige of when Camping just parsed anything that was POSTed. I didn't really think about it when I submitted the patch to test the Content-Type. AFAIK there's no reason not to remove the method test altogether; use those bytes for something more useful. agreed. you can handle request body - @input for any method except the ones that explicitly forbid request bodies (GET, HEAD, OPTIONS/TRACE?..), in one swoop. the MIME test must stay, of course. otherwise when you add support for other MIMEs using #service it silenty fails trying to parse JSON or whatever as QSVars.. ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
