Hi Hu,
It does fragment/defragment messages, but only up to a limit, depending
on the socket type you are using. If you use message oriented sockets,
i.e., SOCK_SEQPACKET,SOCK_RDM or SOCK_DGRAM, it will
only fragment up to MAX_MSG_SIZE, which is indeed 66000 bytes.
If you use SOCK_STREAM, it will fragment up to a size of 100 Mbyte
per sent "chunk". I must admit that I have still not tested this feature
beyond 66k (this is on my TODO list), so you may quite well run into
bugs here. Any feedback on this is welcome.
Regards /Jon
Yin, Hu wrote:
>Hi Jon,
>
>I'm a intern of Intel China Software Lab. Now I'm doing TIPC's
>validation job here.
>
>Today I meet a problem. When I write a little program to send/receive
>different sizes message between two programs there will be error( errno:
>22, "Invalid argument") when the size of message is more than 66000
>bytes.
>
>Doesn't TIPC fragment and defragment messages?
>
>Best regards,
>
>Nick Yin
>
>Intel China Software Lab
>
>The content of this email message solely contains my own personal views,
>and not those of my employer.
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by: SourceForge.net Broadband
>Sign-up now for SourceForge Broadband and get the fastest
>6.0/768 connection for only $19.95/mo for the first 3 months!
>http://ads.osdn.com/?ad_id%62&alloc_ida84&op=click
>_______________________________________________
>TIPC-discussion mailing list
>TIP...@li...
>https://lists.sourceforge.net/lists/listinfo/tipc-discussion
>
>
|