[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
RE: [platform-swt-dev] From Swing to SWT
|
Scott --
We have more or less been repeatedly agreeing on these points. :-)
Cheers,
BradO
> -----Original Message-----
> From: platform-swt-dev-admin@xxxxxxxxxxx
> [mailto:platform-swt-dev-admin@xxxxxxxxxxx] On Behalf Of
> Scott Stanchfield
> Sent: Monday, January 20, 2003 5:44 AM
> To: platform-swt-dev@xxxxxxxxxxx
> Subject: RE: [platform-swt-dev] From Swing to SWT
>
>
> First, most client-side GUI apps are self contained; the UI
> and business logic are on the same machine, so there's no
> wire trip needed. Note that the BL could be talking across a
> wire for other reasons, but it's "normal" to install or send
> the UI and BL for a GUI app.
>
> However, who said the business logic in a GUI app has to be
> (completely) on the server side? You can design an app that
> way, but you can also split the business logic, setting up
> the validation parts in the BL client-side, while the "do it"
> parts are server-side.
>
> Distributed applications don't have to be distributed on
> UI/Buiness Logic/Data Management bounds...
>
> Either way, field-level validation is what I'm talking about,
> and my point is that you need to separate it from the UI so
> you can have alternate UIs... The BL will stay the same, but
> may need slight refactoring if you want to split it. It would
> still work with any UI.
>
> -- Scott
>
> > -----Original Message-----
> > From: platform-swt-dev-admin@xxxxxxxxxxx
> > [mailto:platform-swt-dev-admin@xxxxxxxxxxx]On Behalf Of
> Brad O'Hearne
> > Sent: Sunday, January 19, 2003 9:35 PM
> > To: platform-swt-dev@xxxxxxxxxxx
> > Subject: RE: [platform-swt-dev] From Swing to SWT
> >
> >
> > > That depends...
> > >
> > > I feel *very strongly* that validation should be done
> either only in
> > > the business logic, *or* it must be redone in the business logic.
> >
> > Yes, completely agreed (and was what I originally intended :-). It
> > must necessarily always be validated server-side, regardless of
> > what is done
> > client-side. But with rich-GUI apps, (as opposed to stateless web
> > interfaces) you often want field-level validation (rather than
> > form-level validation). If this is a requirement, you
> either have to
> > put this logic inside the client-side GUI, or make a trip across the
> > wire as you tab from field to field (which is insane). But
> > regardless,
> > the data must be revalidated on the server-side prior to
> persistence.
> >
> >
> >
> > _______________________________________________
> > platform-swt-dev mailing list
> > platform-swt-dev@xxxxxxxxxxx
> > http://dev.eclipse.org/mailman/listinfo/platform-swt-dev
> >
> >
> >
>
>
> _______________________________________________
> platform-swt-dev mailing list
> platform-swt-dev@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/platfo> rm-swt-dev
>