caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
* RAW-sockets
@ 2006-05-18 15:27 Oliver Bandel
  2006-05-18 15:50 ` [Caml-list] RAW-sockets Oliver Bandel
       [not found] ` <ad8cfe7e0605181709y6de7fd24w7e7d51a0cfa8212c@mail.gmail.com>
  0 siblings, 2 replies; 9+ messages in thread
From: Oliver Bandel @ 2006-05-18 15:27 UTC (permalink / raw)
  To: caml-list

Hello,


how to use Eaw sockets from OCaml?

As in raw sockets I have to create the IP-header by myself
I'm wondering how.

IP normally uses 32Bit words, and the parts of it are not
necessarily byte or nibble oriented.
So I have to be able to set some bits directly.
But the OCaml int's is not complete 32 Bits.

How to use the raw sockets then?

Do I have to make a string (for highlevel socket functions)
or int's (read/write) and write that string or int-buffer
into the socket?
So that I write all bytes of the header as if it would be
normal data that I would write to a tcp-socket otherwise?

TIA,
  Oliver


^ permalink raw reply	[flat|nested] 9+ messages in thread

end of thread, other threads:[~2006-05-20 20:57 UTC | newest]

Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2006-05-18 15:27 RAW-sockets Oliver Bandel
2006-05-18 15:50 ` [Caml-list] RAW-sockets Oliver Bandel
2006-05-18 16:08   ` Oliver Bandel
     [not found]   ` <Pine.LNX.4.62.0605181027060.414@camaross.cs.unm.edu>
2006-05-18 21:14     ` Oliver Bandel
2006-05-19  6:14     ` Oliver Bandel
2006-05-19 14:51       ` William D. Neumann
     [not found] ` <ad8cfe7e0605181709y6de7fd24w7e7d51a0cfa8212c@mail.gmail.com>
2006-05-19  6:12   ` Oliver Bandel
     [not found]     ` <ad8cfe7e0605182316l85124c9s5dd588aa89f9c285@mail.gmail.com>
2006-05-19  6:24       ` Oliver Bandel
     [not found]         ` <ad8cfe7e0605182327p3a0d16c4ub43326343347c60c@mail.gmail.com>
2006-05-20 20:57           ` Oliver Bandel

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).