RE: Lightweight definition?
From: Mani, Mahalingam (Mahalingam) (mmaniavaya.com)
Date: Thu, 20 Nov 2003 13:06:28 -0600 (CST)
Real-time is what generically real-time means. Bounded response-time
guarantees in general - failing which, for example, one may lapse
opportunity a time-slot to acquire the wireless medium for transmission
or
risk acknowledging a frame on time.

For details on what functions are characterized by that - I would refer
to the architecture draft.

-mani
> -----Original Message-----
> From: Branislav Meandzija [mailto:bran [at] arraycomm.com]
> Sent: Thursday, November 20, 2003 10:53 AM
> To: Mani, Mahalingam (Mahalingam); James Kempf; gspsl [at] yahoo.com.sg;
LWAPP
> Subject: RE: [Lwapp] Lightweight definition?
> 
> 
> Can you characterize "real-time" in this context and with regards to
> specific functions considered?
> 
> Branislav
> 
> > -----Original Message-----
> > From: Mani, Mahalingam (Mahalingam) [mailto:mmani [at] avaya.com]
> > Sent: Thursday, November 20, 2003 10:35 AM
> > To: Branislav Meandzija; James Kempf; gspsl [at] yahoo.com.sg; LWAPP
> > Subject: RE: [Lwapp] Lightweight definition?
> >
> >
> > Let me try: approximately what makes sense in terms of real-time
> > functions - that cannot tolerate unbound  or not-so
> > well-bound latencies
> > is what I would characterize for correctness. I would agree
> > that it does
> > not apply to real-time functions.
> >
> > In the same breath I would also say some real-time placements in
other
> > than APs does not really mean incorrect - but may lead to
> > constraints in
> > topological separation between AP & AC.
> >
> > -mani
> > > -----Original Message-----
> > > From: Branislav Meandzija [mailto:bran [at] arraycomm.com]
> > > Sent: Thursday, November 20, 2003 10:15 AM
> > > To: Mani, Mahalingam (Mahalingam); James Kempf;
gspsl [at] yahoo.com.sg;
> > LWAPP
> > > Subject: RE: [Lwapp] Lightweight definition?
> > >
> > >
> > > >
> > > > It is important (and should not take long) to get away from the
> > notion
> > > > of 'lightweight'. The lightness is a side-effect.
> > > >
> > > > The main effect is the correct functional separations between AP
&
> > AC.
> > >
> > > I am not convinced that the functional separation is correct. An
> > equally
> > > valid paradigm is
> > > traditional manager/agent. How do we measure "correctness" here?
> > >
> > > Branislav
> > >
> >
> >


Results generated by Tiger Technologies using MHonArc.