Re: [OT] Not everything goes well in Ruby land :-)

--===============0266368311==
Content-Type: multipart/signed; micalg=sha1; boundary=Apple-Mail-32-244091879;
	protocol="application/pkcs7-signature"


--Apple-Mail-32-244091879
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=US-ASCII;
	delsp=yes;
	format=flowed

Hi!

>  That said, what I think WebObjects could steal from Rails is the  
> whole concept of less configuration for the default behavior.  
> There's all this stuff that a production-quality WO program has to  
> implement that should really come pre-done. It's not a lot of code  
> to pull the primary key out of a URL, fetch the relevant object,  
> and pass it to a page component for display, but everyone seems to  
> be constantly reinventing that wheel.

   There's a lot of discussion about if it is dangerous, or not, to  
expose the PKs. I prefer to avoid that when possible, but to be  
honest, sometimes I end up doing stuff that is almost the same as  
exposing the PK (exposing an UNIQUE field that is there exactly to be  
exposed, for example).

   What do you think? What are the goods and the bads of exposing PKs  
in URLs?

   Yours

Miguel Arroz

Miguel Arroz
http://www.terminalapp.net
http://www.ipragma.com




--Apple-Mail-32-244091879--

--===============0266368311==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
WebObjects-talk mailing list
[email protected]
http://www.omnigroup.com/mailman/listinfo/webobjects-talk

--===============0266368311==--