Re: [ns] Application Layer Payload Transfer
Herr Hagen Pfeifer, NS2 is not easy to novice. It's normal that novice people be confusing with some questions and concepts, even network concepts. After months same people that have asked a foo question are now secure, with strong skills and helping another novices with their new foo questions. I was a novice in past, with foo questions and now a I'm a non-novice with less foo questions. My first multicast routing protocol for MANETs is done! Great! Thanks to people that have patience to respond my foo questions with courtesy. Don't do that with NS2 people. NS2 is hard enough. PS.: I'm not talking about your answers to me. I don't care. -- Sidney Doria Redes ad hoc móveis Mestrado em Computação UFCG Brasil Nessa jornada, o conhecimento será o seu escudo... (Mestre dos Magos no episódio do grimoire de ouro)
Re: [ns] Application Layer Payload Transfer
* Sidney Doria | 2008-04-23 13:05:59 [-0300]: We know that NS-2 Transport API to Application layer does not provide a payload transfer. In NS, Transport only tells to the application: hey, a packet with nbytes has arrived. But no data is transfered to the app. I'm using UDP and I need the payload to simulate well my application's behaviour. *** How did you, hard core people, circunvent this issue? You must extend the frame structure and add an additonal field for payload. Grep the source and you will find frame extensions where people add additional QOS flags or piggybacking other information as well. Not that big issue! And... Why NS2 does not provide this?! Why should provide NS2 this? Nobody (except you) need this feature. In the normal case the payload isn't interessing. HGN
