Chronological Thread 

< Chronological >      < Thread >

---

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Lode !

I will skip directly to your questions, as I am not sure I understand
fully, what you were doing :-)

> So the question is now:
> - should the char array only contain the part needed for sin.sin_addr(= the
> IP pointcode address) or should it include more?

The char array should contain a Zero terminated string as
123.252.150.129\0
or
fe80::250:4ff:feee:c783\0
where \0 stands for the zero termination. Anyway these strings are
forwarded to inet_aton()/inet_pton() respectively, which does the
actual conversion.

> - ain't it better to work with the sockunion struct instead of the
> char/byte array. At least the compiler get something more to do than
> generating assember code. It can warn you if you did provide the wrong
> parameter to your function. (I like strong type checking anyway by a
> compiler)

Well, we had some lengthy conversation with Wolfgang Schrüfer
and he felt it was better to have an sctp.h that did not include
any OS specific stuff (indeed it is plain C now).
Internally we use the struct sockunion - so there is one conversion
involved inside the library from string to struct sockunion
per new SCTP instance (plus another one in your application
maybe). As that should not happen very often I don't think it
is a performance problem.

Anyway, if the conversion fails, the function sctp_registerInstance
returns 0 as an error code - and you should know that the
registration has not worked.

Regards,

Andreas Jungmaier

- ----------------------------------------------------------------------------
void hamlet()
{#define question=((bb)||(!bb))}
- ----------------------------------------------------------------------------
Andreas Jungmaier, Dipl.-Ing.
University of Essen email:
ajung AT exp-math.uni-essen.de
Computer Networking Technology Group Tel. : +49 (0201) 183-7636
- ----------------------------------------------------------------------------
PGP Public Key and Fingerprint: see http://www.exp-math.uni-essen.de/~ajung
- ----------------------------------------------------------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD4DBQE6yzUld2Uw+xBvGUIRAnnyAJ96a6Af9aFrAa7bKIe8YnTA019e0ACUDSlH
JWVjAlEXk3/zznSmSPaLLQ==
=FIxu
-----END PGP SIGNATURE-----

---

• [SCTP-Discussion] Is the timer_list initialised?, Coene Lode, 04/02/2001
  • <Possible follow-up(s)>
  • RE: [SCTP-Discussion] Is the timer_list initialised?, Coene Lode, 04/04/2001
    • Re: [SCTP-Discussion] Is the timer_list initialised?, Andreas Jungmaier, 04/04/2001
  • RE: [SCTP-Discussion] Is the timer_list initialised?, Coene Lode, 04/04/2001
    • Re: [SCTP-Discussion] Is the timer_list initialised?, Marc Boucher, 04/05/2001
      • Re(2): [SCTP-Discussion] Is the timer_list initialised?, Michael Tüxen, 04/05/2001
        • Re: Re(2): [SCTP-Discussion] Is the timer_list initialised?, Marc Boucher, 04/05/2001
      • Re: [SCTP-Discussion] Is the timer_list initialised?, Andreas Jungmaier, 04/05/2001
        • Re: [SCTP-Discussion] Is the timer_list initialised?, Marc Boucher, 04/05/2001
          • [SCTP-Discussion] Strings vs. Sockunion, Andreas Jungmaier, 04/05/2001
  • RE: [SCTP-Discussion] Is the timer_list initialised?, Wagner, Joel, 04/05/2001
    • Re: [SCTP-Discussion] Is the timer_list initialised?, Marc Boucher, 04/05/2001
  • RE: [SCTP-Discussion] Is the timer_list initialised?, Wagner, Joel, 04/05/2001

---

Archive powered by MHonArc 2.6.19+.