Hey I dig objects too, why do you think I work for GemStone?
However the problem is that without a "value holder" approach you end up
serializing a lot of extra stuff to the client. Depending on the scale of
things this can be a performance and scalability crusher. "Good OO" has to
be balanced with pragmatism when the distributed nature of these
environments is taken into consideration.
When the "network really Is the computer" this may change. But we ain't
there yet! Are the bandwidth guys listening? ;-)
Regards,
-Chris.
> -----Original Message-----
> From: Floyd Marinescu [SMTP:[EMAIL PROTECTED]]
> Sent: Wednesday, April 26, 2000 5:42 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Cached Rowsets-do we need to use them
>
> >What happen to OO? I prefer to send my domain objects (State or Details
> >objects, whatever you call them) to the client and rely on an good OOUI
> to
> >solve the problem of mapping each object into what component it needs to
> be
> Agreed. This is simpler and more effective a mechanism. I don't
> understand
> why anyone would take data out of an object and turn it into a row. You
> lose
> both compile-time verification of your code and it becomes less
> maintainable.
>
> Floyd
>
> ==========================================================================
> =
> To unsubscribe, send email to [EMAIL PROTECTED] and include in the
> body
> of the message "signoff EJB-INTEREST". For general help, send email to
> [EMAIL PROTECTED] and include in the body of the message "help".
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
