RES: RES: Why object's name is so short?

[Wendell Pereira da Silva]

-----Mensagem original-----
De: rtems-users-bounces at rtems.org [mailto:rtems-users-bounces at rtems.org] Em nome de Mozzhuhin Andrei
Enviada em: segunda-feira, 24 de janeiro de 2011 16:01
Para: rtems-users at rtems.org
Assunto: Re: RES: Why object's name is so short?

> I guess this way it keeps low memory profile.
> IMO, this is irrelevant since we can track name of objects by using a document (i.e. a user manual) in large embedded software projects. 
> 


What the rules are in your applications?


Let nnn an integer number greater than or equals to zero:
 - Real-time tasks (rate-monotonic): Tnnn
 - Application tasks: tnnn

For example, how are you called the tasks for client TCP sessions?

Well, IMO, one task per TCP session is is not so scalable, so to speak. One task using socket select() would be fine, instead. But, snnn, 's' for session, would be good, wouldn't? Unless you expect an embedded system be able to manage more than a thousand sessions! :-)

-- 
Andrei Mozzhuhin

_______________________________________________
rtems-users mailing list
rtems-users at rtems.org
http://www.rtems.org/mailman/listinfo/rtems-users