Chronological Thread 

< Chronological >      < Thread >

---

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


> Well believe it or not, my SCTP related work is also mandated by Siemens!
> And on the embedded system where they use the library (a 50mhz MPC860
> board) repetitive string manipulations are a non-negligible waste of CPU
> resources.
>
> > And there were surprisingly few comments about the API, when we
> > discussed it before - well except for some of the Siemens developers,
> > notably Wolfgang Schrüfer who had some very good remarks.
>
> Unfortunately I was too busy at the time to follow and participate in
> those discussions, but they surely lead to many good improvements.
>
> However the usage of strings when processing packets leaves to be desired..

If you want to look at the current version (more current than
sctplib-1.0.0-pre8 -- they are named pre8a, pre8b, pre8c etc.)
you can have a look at
ftp://tdrwww.exp-math.uni-essen.de/pub/unix/sctp/

The name conversion is now only done once, in the interface
functions that pass Strings (well except for maybe a log-function
here and there, which you can safely comment out, anyway).

I see your point though (and that of Lode and others). I might
change the interface back to sockunion's, BUT :
if I do so, I will do so only AFTER the M3UA bakeoff has happened
and we have released a stable version sctplib-1.0.0
Any API changes will not go into the 1.0.0 tree and will not be done
before the upcoming SCTP or M3UA bakeoffs.

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

iD8DBQE6zGNUd2Uw+xBvGUIRAmjBAJ0djXnviLJY0XsU6sDjyWrLKqqMZwCeNz/2
JAeJ59NebiBzTKLYGsWF3uI=
=k8dg
-----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+.