in reply to Re: Re (tilly) 1: Rather complicated OO (and RPC) question...
in thread Rather complicated OO (and RPC) question...

What kind of machines are you talking about?

You mentioned Windows. The GUI on Windows continually takes up several times the resources of a webserver. Any Windows machine with enough resources to run Office can function perfectly well as a webserver. Or to put it another way, a P100 with 32 MB of RAM is overkill for running a low-volume webserver, as long as you are using an OS that is not resource heavy. (Erm, you mentioned Windows? Nevermind.)

I highly doubt that server resources will be a constraint preventing your running a webserver.

Now your not knowing WWW is a good argument against. But on the other hand the amount you need to learn to write a CGI is less than the amount you need to learn to write a custom client-server application...

  • Comment on Re (tilly) 3: Rather complicated OO (and RPC) question...

Replies are listed 'Best First'.
Re: Re (tilly) 3: Rather complicated OO (and RPC) question...
by Necos (Friar) on Mar 05, 2002 at 15:09 UTC
    My job computers are all WinNT/2000/XP for the desktops and laptops, WinNT 4 for the servers. I don't trust a webserver to run well in NT period (it can barely run an IRC server for crying out loud). Like I said before, I think the custom client/server model will be the best idea for this situation since I can have a VERY light setup (remember, this stuff is running under Windows). The program will be running on multiple servers, as to avoid blocking up the whole time in order to run all the RPC stuff.

    Server specs are something in the order of:
    1 dual p3-700 with 1 gig of ram (no problem for this server whatsoever), 1 p2-400 with 128 megs of ram (this one could have problems if bogged down for too long), 1 p2-233 with 256 megs of ram (this one is quite dead if it gets hit with a lot of requests), and 1 p2-233 with 128 megs of ram (if this one also gets hit with too many requests, it will hurt badly).

    I always have to keep in mind that there are other services running on these servers. Those services also receive priority over everything else. It sucks that running Windows on these servers takes away a lot of system resources. If I could go back, I would probably have gone the Linux route with directory permissions for each student, along with pushing X sessions down to the client. Of course, the students at my job are computing "n00bs," so it may have been more appropriate to use Windows. Nothing wrong with being a "n00b." We all had to start there sometime.

    If anyone is willing to take a look at the RPC code here in the examples zip file (tarball if you're in BSD/Linux) and has any insight into how to restructure the RPC and/or Msg modules to accept OO, please let me know. Maybe I can get there myself, but more than likely not.

    As always tilly, you've given me advise that's helpful (even if it's not the solution for world hunger), and I'm thankful for it. If you should come up with any "Einsteinian insight" (as my E&M professor likes to say), please toss it my way.

    Thanks,

    Theodore Charles III
    Network Administrator
    Los Angeles Senior High
    4650 W. Olympic Blvd.
    Los Angeles, CA 90019
    323-937-3210 ext. 224
    email->secon_kun@hotmail.com