Re: Best approach?

So i should send the variables that i need when i need them and load them
into objects at the other side rather than the whole object via
serialisation?

So best practice is lots of small packets rather than less packets but
larger sizes? is that right

"Dan" <dvazanias@xxxxxxx> wrote in message
news:ukyEYKRHGHA.240@xxxxxxxxxxxxxxxxxxxxxxx
>I presume that to send anything i have to convert it into bytes, send it
>then extract it at the other end.
>
> Is it possible to say have a class myClass and send it as an object
>
> so in pseudo code
>
> SendData (myClass);
>
> then at the other end
>
> myClass _obj = new myClass();
> _obj = ReceiveData(myClass);
>
>
> Is that possible? or do i have to send each part of it separately,
> variable per variable etc and then rebuild it at the other end? Could
> someone provid sample code if possible, c# .
>
> --
> Dan
>


.

Relevant Pages

  • Re: Best approach?
    ... Be aware that serialization demand your class be inhereted from ... > So best practice is lots of small packets rather than less packets but ... >> Is it possible to say have a class myClass and send it as an object ... >> someone provid sample code if possible, ...
    (microsoft.public.win32.programmer.networks)
  • Re: Best approach?
    ... packing, alignment, byte ordering (big-endian/ little-endian) at least. ... You suould define an 'on-wire' format (in network byte order) for the data ... > Is it possible to say have a class myClass and send it as an object ... > someone provid sample code if possible, ...
    (microsoft.public.win32.programmer.networks)
  • Re: Best approach?
    ... Vadym Stetsyak aka Vadmyst ... >I presume that to send anything i have to convert it into bytes, ... > Is it possible to say have a class myClass and send it as an object ... > someone provid sample code if possible, ...
    (microsoft.public.win32.programmer.networks)