Open source BSD like socket, tcp, udp library.

Go To Last Post
4 posts / 0 new
Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Ok boys n gals...over the years I have developed a tcp/udp/ip stack with BSD like socket interface and successfully used it with few embedded projects.

I think its about time I share it with the community. I wondered what sort of interest there may be on such a thing, given the existence of uip, lwip and thw likes.

I am also wondering if there would be any licensing implications as it used BSD like socket interface. Certainly the implementations are mine.

Would github be the best way to share such a thing?

Any advise welcome...

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I wondered what sort of interest there may be on such a thing, given the existence of uip, lwip and the likes.

I dunno.  What does it do that's special?

 

I am also wondering if there would be any licensing implications as it used BSD like socket interface.

The BSD license is very permissive.  I think that even if you had copied, say, socket.h from the berkeley code, all you'd have to do is keep their copyright IN THAT FILE, and perhaps mention them in the documentation (which you've already done.)

 

 

Would github be the best way to share such a thing?

Github is a fine way to share such things.  No need to spend time arguing over "best" :-)

 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

My advice would be to put it up on Github. if there are licensing implications, then hopefully someone will advise you of this. I'd be thinking that 'BSD like' is describing an interface, not an algorithm, so one might think that that is not copyright-able. Besides, the BSD license is fairly liberal.

My questions are - how is this any better than the other implementations that are available? How have you validated it? What does it comply with? Or does it 'just seems to work ok". For those of us who have used UiP, we know it is cheap n cheerful. There's a few things it doesn't do, but these are stated.

 

Note the use of 'advice' and 'advise'. One letter makes a difference.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

luvocean1 wrote:
given the existence of uip, lwip and the likes.

As the others have suggested, these are well-established, widely-used, mature and respected stacks - so the key question is, why would people choose your "newcomer" over these?

 

What significant advantage(s) does it offer?

 

How will it be supported?

 

Kartman wrote:
How have you validated it?

A very important question!

 

Making something that seems to "work" in the nominal case is the easy bit - having it properly handle all the corner cases is the hard bit!