we frequently start presentations with full documents. some examples: 1. the wb pages are prepared beforehand so expedite the meeting 2. we use the wb for doing presentation so the entire presentation is loaded at the beginning of the meeting 3. sometimes our meetings carry over several days so we reimport them each morning because we make changes offline after each day¹s discussions if the pace of the changes doesn¹t keep pace with the discussion or the changes upon review don¹t mesh up with what people said. hey people make mistakes too :)
The above reasons and the problems with satellite/mobile communication is why we implemented history support in our whiteboarding protocol. boyd On 3/3/08 6:51 PM, "Fabio Forno" <[EMAIL PROTECTED]> wrote: > On Tue, Mar 4, 2008 at 12:23 AM, Joonas Govenius > <[EMAIL PROTECTED]> wrote: >> > >> > If the extra bandwidth really is such a problem we could define an >> > implicit way of creating the objects out of a chunk of XML as I've >> > mentioned but it doesn't seem worthwhile to me at this point. > > In whiteboarding, where we usually start with and empty xml document, > there aren't problems I think. However there are also other > application fields, such as distributing, monitoring and update of > remote configuration files, where we start from non empty documents > and sometimes we need to change significant parts of them. In this > case the overhead could be high and costing, especially if we are > controlling remote nodes with mobiles connections. > > -- > Fabio Forno, Ph.D. > Bluendo srl http://www.bluendo.com > jabber id: [EMAIL PROTECTED] >
