It depends on the component. It is easier with auto, but you don't have as much control so it might be clearer what is happening with non-synch. You don't need any ivars to have bindings with non-synch. If you know your component won't ever takeValues or invoke an action, you can just do valueForBinding() and never actually push state up which might save time. But again WO4 is so fast, I would think about non-synchs from a control standpoint as a motivation rather than a performance one. "Mark F. Murphy" wrote: > > At 7:59 PM +0100 3/17/99, Helge Hess wrote: > >The synchronization overhead can be heavily reduced by the WO4 > >non-synchronizing components, look into the WO4 ChangeLog file for a > >description. This is much like writing a dynamic element. > > Is there a plus to turning off auto-syncing? What are the cons? > > mark > --------------------------------------------------------------------------- > Mark F. Murphy, Director Software Development <mailto:[EMAIL PROTECTED]> > Tyrell Software Corp <http://www.tyrell.com> > PowerPerl(tm), Add Power To Your Webpage! <http://www.powerperl.com> > --------------------------------------------------------------------------- > Member of Families Against Internet Censorship: rainbow.rmi.net/~fagin/faic
