1. RE: Linux sockets
Peter.Blue at legend-i.demon.co.uk wrote:
> Hello everyone,
>
> Does anyone know how to send text/data through Linux sockets using
> Euphoria ?
>
> Regards
> --
> Peter Blue
> IT Director - Legend Interactive Ltd
> Technical Director - Platinum Communications Ltd
>
> Please visit our web sites
> http://www.yes-property.co.uk - International Estate Agents
> http://www.legend-i.demon.co.uk - Legend Interactive Ltd
Pete:
Goto the archive and take a look at this download:
http://www.rapideuphoria.com/rdc.zip
Bernie
2. RE: Linux sockets
On 7 Nov 2002, at 18:43, Bernie Ryan wrote:
>
>
> Peter.Blue at legend-i.demon.co.uk wrote:
> > Hello everyone,
> >
> > Does anyone know how to send text/data through Linux sockets using
> > Euphoria ?
> >
> > Regards
> > --
> > Peter Blue
> > IT Director - Legend Interactive Ltd
> > Technical Director - Platinum Communications Ltd
> >
> > Please visit our web sites
> > http://www.yes-property.co.uk - International Estate Agents
> > http://www.legend-i.demon.co.uk - Legend Interactive Ltd
>
> Pete:
> Goto the archive and take a look at this download:
> http://www.rapideuphoria.com/rdc.zip
That would be a great lib for *nix people to put their own Ai worm into a
central worm bed.
Can i beg/pay anyone using nix to make it run as a remote http relay with a
spot for me to plug in other functions between the relay in/out parts? Even if i
recode it, i cannot justify testing code on a box i don't own, possibly
crashing it when others are using the box. This code doesn't look async, is
it? If not, can it be made async? i cannot allow it to use 100% of cpu on a
remote shell.
Kat
3. RE: Linux sockets
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
4. RE: Linux sockets
- Posted by irv at take.maxleft.com
Nov 09, 2002
Martin Stachon wrote:
>
> You shouldn't be able to nuke a Linux box unless you are root or a
> hacker 
>
Depends on your definition of 'nuke'.
It's possible to write a loop that will use 99.99% of the CPU cycles,
and almost as easy to write a loop that will eat up all memory,
plus all virtual memory. Either way, that effectively stops all other
processes, including any chance to kill your runaway Euphoria program.
Any user can do this, root permission is not required.
I have had Linux run for 30+ days, until a programming error caused
one of the above problems. Only way out is to reboot, which may
create disk errors. So be careful.
Irv
5. RE: Linux sockets
jbrown105 at speedymail.org wrote:
[snip]
> I can confirm this. I found a port of euTCP4u to linux rather simple.
> I did it in 20-30 minutes, but was discouraged from using it due to its
> lack of features, and am now writing such a library for *nix in pure
> Eu.
>
> jbrown
Can you send your Linux version to me then I can update the distribution
to include both.
Did you change euTcp4u using platform() so the same works on Win32 and
Linux? Either way I'm sure it's not difficult to apply your changes
to the master source using platform().
Do you have the Tcp4u Linux shared library that you could send as well??
You can send any files to ray at rays-web.com
Thanks,
Ray Smith
http://rays-web.com
