On 1 févr. 07, at 14:17, Jerry W. Walker wrote:
A true DoS attack will probably hit your main page as well, but if
it's a DDOS attack, although it's really a different issue that has
to be handled upstream of your application server to get back on
the air, at least it won't bring your ap
Alternatively, you could just create your own subclass of
EOGenericRecord and for all your EO's and put cover methods for the
EOUtilities methods in there. Implementing that is easy if you are
using eogenerator just change the extends in the generation gap
template and regenerate.
Lo
Hi!
You could set primary keys as class properties - provided you don't
go modify their values.
I'd say the best approach - if you really, really need those values -
is to set them as read-only class properties. Make sure your
eogenerator template checks for read-only attributes and omits
Hi Mark,
Before setting primary keys as class properties I would really
question my design. This question typically occurs when you use the
primary to convey meaning about the object and this can usually
better be expressed in the object itself. This will give you a better
object design a
Hi Pierre,
First off, thanks for the response (and thanks to the others who
responded earlier). It is good to hear from someone at Apple who is
familiar with the code. It sounds like the smart thing to do is not
to add keys as class properties directly, since EOF might have some
branch
