How about the potential for action-class re-use in "non-servlet"
applications (ie: java-gui clients)?

- Frank

> -----Original Message-----
> From: Peter Lynch [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, June 14, 2001 3:32 PM
> To: [EMAIL PROTECTED]
> Subject: Reasons For Action Classes
> 
> 
> Hi,
> 
> Someone asked me why the need to separate action
> classes from screen class code. In other words, they
> were wondering why not have the screen classes do all
> the work? I was brain dead at the time so I think I
> did not give a very compelling argument why....
> 
> So can anybody offer some compelling
> reasons/advantages for this design as opposed to
> having the screen classes do all the work of putting
> and getting?
> 
> Thanks,
> 
> Peter
> 
> __________________________________________________
> Do You Yahoo!?
> Spot the hottest trends in music, movies, and more.
> http://buzz.yahoo.com/
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to