Reading Programming

Why not write the server and client in Java?

Because I suck at Java and wouldn't have a say then. ;-)

No, honestly, if everybody wants Java I guess I could live with that. I've just suggested C because it's fast, very cross-platform and I know it well. :-)
The problem is, will everybody (especially Windows users) have a Java runtime environment? Or are you using a Java compiler that produces OS-specific binaries?

I don't know anything about Kylix. What language is that anyway? Pascal???

It's supposed to be the Linux version of Delphi, which basically is a RAD tool for Object Pascal. (Before flaming me, please note that the Delphi compiler currently produces the fastest compiled code for Windows. :-) ) I'm currently trying to install Linux on my main machine and try it out, but my unusual disk partitioning is still causing me trouble. I'll let you know when (if) I can give Kylix a try.

When life hands you a lemon, that's 40% of your RDA of vitamin C taken care of.

The problem is, will everybody (especially Windows users) have a Java runtime environment? Or are you using a Java compiler that produces OS-specific binaries?

JRE on windows runs perfectly fine. The version that one can download from SUN's website is pretty stable. For development purposes, I have always used JBuilder for windows, and never had any problems with it's compiler or it's runtime environment.

Java compiler always converts code to OS-independent byte-codes. And, the JRE which interprets the byte-code is OS-dependent. So, the same byte-code can be executed by any JRE.

Love is blind, but marriage is a real eye opener.

This post was deleted by request of the author.

A couple benefits that Java would give us is that the server could run on a FreeBSD machine or a Linux machine or a Windows machine. One client would also run on each of these platforms out of the box.

Just keep in mind that we're talking about a P75 with 16Megs of RAM. If you want to run a Java app on it, we either need another server or some serious upgrading. I'm hoping to upgrade to 64MB soon, but Java isn't exactly known for economic use of CPU resources either, so...

When life hands you a lemon, that's 40% of your RDA of vitamin C taken care of.

This post was deleted by request of the author.

However keep in mind that a server written in Java will mean that we may not need your P75 with 16 megs of RAM.

Hmm, one can also write pretty platform-independent ANSI-C code. :-)
But don't worry, I just keep telling that because so far nobody besides me has offered a server.
I could do the C stuff or even explain you some things. OTOH it's probably better to stick to one single language for the server. Everything else might quickly get complicated. When the majority decide that this be Java, that's perfectly okay for me. After all it's a chance for me to dissect your code and learn something. :-)

I'll see what I can do to upgrade the server. Maybe I can even get my hands on another, more powerful machine. Most of the CPU-hogging stuff will be done on the clients anyway.
Or does anybody else have a more powerful machine with a permanent 'net connection?

When life hands you a lemon, that's 40% of your RDA of vitamin C taken care of.

This post was deleted by request of the author.

I will upgrade my server ASAP then. :-)

Is it too early to create shell accounts for you?

When life hands you a lemon, that's 40% of your RDA of vitamin C taken care of.

This post was deleted by request of the author.

we are talking about a p75, right ?
and you are planning to do the server in java ?

i mean .. the 'i need lots of resources' - java ? the 'i create ~20 threads to do some simple http-serving' - java ?

i recommend using c and a really simple protocol.
some udp messaging would be the protocol of my choice.
as soon as the way of communication is defined, publish the specs so anybody can write his own client :)

Note that, u. o. u., s. is not a computer program and his answers might not always be appropriate.