OpenEuphoria

RE: Linux sockets

• Posted by Ray Smith <smithr at ix.net.au> Nov 08, 2002
• 413 views

Kat wrote:

[snip]
>like tcp.e and tcp4u does for windoze. 

as a side note euTcp4u uses the C library Tcp4u ... which is a cross 
platform library.  As far as I can tell it is mainly used under Linux.
Libnet is also cross platform.  I had always intended to port the 
Euphoria
versions to Linux ... even "tried" a few times but failed due to my 
lack of knowledge :( .

I know Tcp4u and Libnet both have missing features for "server based" 
work ... but there are other TCP libs out there that might have the 
features your after.  It would be a "simple" :) matter of wrapping
an already existing Tcp library.

Even just getting some Linux sockets code and writting your own C 
library and making a wrapper is a possability.

A few hours searching on the net will probably find half a dozen Linux
based TCP libs.  A said simple before ... it probably wouldn't be ...
but it might be your only option.

Kat, if your serious about your project you will need at least a Linux
PC at home and better FreeBSD.  You should be able to buy second 
hand computer for between $100 - $200 (here in Aus anyway) that could 
run Linux or FreeBSD as a server.  It will probably be a nightmare to
setup and configure ... but that's the price you'll have to pay.  If
your going to run apps on *nix based OS's ... your going to have to 
learn about them.

Without a doubt you won't be able to rely on other people to create
libs and then test them AND your progams for you.

I'm sure you will get some help ... but what happens after it is 
running on the live server ... and a problem occurs ... and no one is 
around to help you test????  What do you say to the client ... sorry 
I can't test it?  I can't run it anywhere?  I don't know what's 
happening?  In the world I live in ... you and your program will be 
thrown out of there quicker then your client can type:
"kill -9 eu_server"

Any commercial app (or semi commercial app) you write YOU must be able
to support.  If you can't your app and you won't succeed.

You have two choices:

1.  Set yourself up to be able to develop and support the app you want,
or if you can't do that

2.  Develop an app you can develop and support on your own.

 
This email probably sounds a little harsh ... and it probably is,
the reason? ... we don't live in wonderland, people aren't going to do 
much more than give you some advice or answer some specific questions.
If you and your app are going to succeed it will be because you did the
hard work.

Kat, I hope (actually I know I haven't!) discouraged you.
I really hope you succeed.  I just think you should be realistic about
what you expect from other people and commercial software development.

Regards,

Ray Smith
http://rays-web.com