On 4/24/07, Tim Pope <[EMAIL PROTECTED]> wrote:
> The disadvantage to this method is that "new" doesn't fit cleanly into
> the four CRUD actions. This was accepted as a necessary compromise
> for interactive uses, but now it's creeping into the API as well.
No compromise needed. Restful controll
I'm working on a plugin for running a Rails app directly in JRuby on
Rails with Jetty. (I'm calling it Retty.) I would ideally want to get
to the point where you could just do:
script/plugin install retty
jruby script/server retty
Unfortunately the server command is horribly unextensible. It wou
> Automatically generating a schema seems like overkill, given that the
> schema for your models changes rarely, what's wrong with just a human
> readable API doc page.
Because that's a lot of work, and a standard format makes that work
unneeded. The Beast forum doesn't need to publish an API do
On Tue, Apr 24, 2007 at 10:24:55AM -0700, Eric Mill wrote:
> > I just don't really see how this enables anything new, surely
> > anything
> > javascript can do with the schema document, could also be done with
> > the xml document received in response to /foos/1.xml?
>
> This only works if there
On Sat, Apr 21, 2007 at 11:33:35PM -0500, Tim Pope wrote:
> On the subject of XML schemas, the biggest missing piece of the puzzle
> is a way to get the appropriate attributes on the root element for
> records. I am thinking an interface would look something like
>
> @people.to_xml(
> :root_at
The build failed.
See http://cruisecontrolrb.thoughtworks.com/builds/RubyOnRails/6574 for details.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" group.
To post to this group, send email to rub
The build failed.
See http://cruisecontrolrb.thoughtworks.com/builds/RubyOnRails/6573 for details.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" group.
To post to this group, send email to rub
The build failed.
See http://cruisecontrolrb.thoughtworks.com/builds/RubyOnRails/6572 for details.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" group.
To post to this group, send email to rub
The build failed.
See http://cruisecontrolrb.thoughtworks.com/builds/RubyOnRails/6576 for details.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" group.
To post to this group, send email to rub
The build failed.
See http://cruisecontrolrb.thoughtworks.com/builds/RubyOnRails/6575 for details.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" group.
To post to this group, send email to rub
Unspoken inference: the routing code would need refactoring/reducing
to support thread-happiness/safety.
Nic
On Apr 24, 9:20 am, Dr Nic <[EMAIL PROTECTED]> wrote:
> Page 24 of Ez's Mongrel presentation (http://brainspl.at/
> mongrel_handlers.pdf) suggests he gets good throughput by doing
> routi
Page 24 of Ez's Mongrel presentation (http://brainspl.at/
mongrel_handlers.pdf) suggests he gets good throughput by doing
routing processing etc before starting the mutex lock.
[I've not looked at this code for Rails nor Merb] - is this something
we can port to Rails? Anyone written about this al
12 matches
Mail list logo
