Rails - Feb 2006 - Controller methods

I am not clear on what makes a controller method available as an URL. More
specifically, I''m not clear on how to prevent methods from being
available
as URLs.

I am working on a simple web API framework (home-rolled rather
than SOAP or XML-RPC) that provides little more than a high-level messaging
system between JavaScript and Rails. My ApplicationController will
implement the only methods that should be available via HTTP, but the other
controllers will need to implement methods that the HTTP-accessible methods
will call. Is it as simple as making the separate controllers'' methods
all
protected and private?

--Greg

Yes, I think ''private'' methods are not reachable by a URL.

_Kevin

On Monday, February 27, 2006, at 6:25 PM, Gregory Seidman
wrote:
>I am not clear on what makes a controller method available as an URL. More
>specifically, I''m not clear on how to prevent methods from being
available
>as URLs.
>
>I am working on a simple web API framework (home-rolled rather
>than SOAP or XML-RPC) that provides little more than a high-level messaging
>system between JavaScript and Rails. My ApplicationController will
>implement the only methods that should be available via HTTP, but the other
>controllers will need to implement methods that the HTTP-accessible methods
>will call. Is it as simple as making the separate controllers''
methods all
>protected and private?
>
>--Greg
>
>_______________________________________________
>Rails mailing list
>Rails@lists.rubyonrails.org
>http://lists.rubyonrails.org/mailman/listinfo/rails




-- 
Posted with http://DevLists.com.  Sign up and save your time!