1  |   Order by index

Apr 9, 2004, 7:55am

After what I saw during the SW City bash, 30 or so people downloading cells
packed with info, which made it take forever (10 minutes +) to load an area,
a thought crossed my mind.

Is this possible?
"Let's raise prices 350%. That will lower the number of people coming here,
and we'll still maintain a steady income. The fewer number of people will
allow us to downgrade servers, saving money"

Could it be that AWI downgraded the servers, and now it just would be
impossible for them to handle the number of people we used to have in 2001?

Apr 10, 2004, 8:46am

I heard AW were on DSL

~John

[View Quote]

Apr 10, 2004, 9:28am

AW used to handle over 100 people on average in Alpha World. Just get 30
people all loading medium density cells in SW City, and all hell breaks
loose (uber long load times) that lasted until everyone finally left the
party. I really think AW downgraded their servers. What else would explain
it?

Apr 10, 2004, 9:49am

I dont think DSL Would hold 100 users..
I do hope you mean 1.5Mbit DSL at the least.

--

Ry
#323710
Visit Ocean City! Luxury in AW - www.oceancity.tk
AIM: RyAWU - ICQ: 256-319-414
[View Quote]

Apr 10, 2004, 12:43pm

AW used to handle 100 people on average he said... not that they do now.

~John

[View Quote]

Apr 10, 2004, 4:13pm

Simple caching would solve this.

- MR

[View Quote]

Apr 10, 2004, 5:06pm

A company like AW should at least have a T3 connection which is about 45
Mbps; Ferruccio was just talking about their server hardware though, but
you guys bring up a good point. The monthly cost of a T3 service is
expensive. It's reasonable to believe they knocked it down to a T1 or
something seeing as how the public worlds are far less demanding than they
use to be.


[View Quote]

Apr 10, 2004, 5:14pm

Come to our event! Here is your personalised schedule.

Fri 2:21pm VRT - Your turn to cache
Sat 10:00pm VRT - Opening ceremony

[View Quote]

Apr 10, 2004, 6:53pm

Should of had you plan the schedule, Rossy =P


[View Quote]

Apr 11, 2004, 6:14am

Well, that's a really bad sign if AW does not have the bandwidth to prepare
for any potential increase in users. Could this be why they make absolutely
no effort in advertising? Maybe AWI doesn't *want* AW to have as many users
as they used to be, which, if you ask me, means that they don't *want* AW to
be as fun as it used to be. Even though more features are nice, it's the
*people* that make AW fun.
[View Quote]

Apr 11, 2004, 7:16am

[View Quote] > Well, that's a really bad sign if AW does not have the bandwidth to prepare
> for any potential increase in users. Could this be why they make absolutely
> no effort in advertising? Maybe AWI doesn't *want* AW to have as many users
> as they used to be, which, if you ask me, means that they don't *want* AW to
> be as fun as it used to be. Even though more features are nice, it's the
> *people* that make AW fun.

/* Written by Bowen (4/11/2004), not tested, should work on all
platforms capable of compiling/linking/whatever C++; capable of
storing integer values of 1 and anything other than 1. Try not to
get technical with shit like "Oh this won't compile on bling bling
shithole OS X7vZ1 because I'm a jackass and like to be difficult."

I'll give you a linux ISO if you really can't afford free, and need
to be that person.

This code is freeware, but include my name in comments/credits
wherever used.

BTW, whitespace sucks in newsreaders.
*/

#include <iostream>
using namespace std;

#define ENZOWantsMoney TRUE
#define ENZOWants3cars TRUE

int main()
{
int InputBuffer;

cout << "Does AWI want more users?(1 is yes, anything else is no)";
cin >> InputBuffer;

if( ENZOWantsMoney == 1 &&
ENZOWants3cars == 1 &&
InputBuffer == 1 )
cout << "You're in luck, more users let's E N Z O have
his cars and money!";
else
cout << "Damn, that's not going to work out in the long run.";
return 0;
}

Apr 11, 2004, 7:16am

Word wrap totally fucked up my code. Oh well, it should technically
still work.

Apr 11, 2004, 7:19am

[View Quote] > Word wrap totally fucked up my code. Oh well, it should technically
> still work.

How about... now:

/* Written by Bowen, not tested, should work on all platforms
capable of compiling/linking/whatever C++; capable of storing
integer values of 1 and anything other than 1. Try not to get
technical with shit like "Oh this won't compile on bling bling
shithole OS X7vZ1 because I'm a jackass and like to be difficult."

I'll give you a linux ISO if you really can't afford free, and need
to be that person.

This code is freeware, but include my name in comments/credits
wherever used.

BTW, whitespace sucks in newsreaders.
*/

#include <iostream>
using namespace std;

#define ENZOWantsMoney TRUE
#define ENZOWants3cars TRUE

int main()
{
int InputBuffer;

cout << "Does AWI want more users?(1 is yes, anything else is no)";
cin >> InputBuffer;

if( ENZOWantsMoney == 1 &&
ENZOWants3cars == 1 &&
InputBuffer == 1 )
cout << "You're in luck, more users let's E N Z O have his cars and money!";
else
cout << "Damn, that's not going to work out in the long run.";

return 0;
}

Apr 11, 2004, 12:21pm

Arnt TRUE and FALSE defined in MFC, in which case using stdafx would be
required... with the standard

#define TRUE 1
#define FALSE 0

Whereas C++ uses proper evaluation of the terms 'true' and 'false' where

#define true !0
#define false 0

?

Or that could just be VC++ talking.

- MR

[View Quote]

Apr 11, 2004, 5:34pm

[View Quote] > Arnt TRUE and FALSE defined in MFC, in which case using stdafx would be
> required... with the standard
>
> #define TRUE 1
> #define FALSE 0
>
> Whereas C++ uses proper evaluation of the terms 'true' and 'false' where
>
> #define true !0
> #define false 0
>
> ?
>
> Or that could just be VC++ talking.

#define TRUE 1
#define FALSE !1

true is _always_ 1, and false is _always_ not 1. So I was taught, I'm
pretty sure that's the standard.

If you test the program and try to run it with true instead of 1 in all
the places I put 1, and then input things that are not 1, you will get
the "else" statement.

I use TRUE whenever I use #define statements to help me keep track of
things. As far as I'm aware, when in if statements, they are delt with
the same as "true". At least gcc treats them like that. Please note, I
don't use MFC, so any reference to it will lead you in circles with
talking to yourself.

VC++ probably doesn't treat it the same, I don't know -- only weirdos
use VC++.

Apr 11, 2004, 6:39pm

I was always under the distinct impression that the C++ rules of engagement
so to speak defined that the actual types types true and false meant 'value
present' or 'value not present' for false. While true is 1 for maths
operations etc, in logic operations it is defined as 'anything not zero' so
to speak.

if (1)
printf("The result is true\n");
else
printf("The result is false\n");


- MR

Apr 11, 2004, 7:19pm

A definition in MFC - especially there - is not a proof
(or is it "proove"?) for any standard.


Defining TRUE as 1 might work on some systems, some others
use _all_ bits set for the TRUE value (on CPU level). So
this definition would meet the standards a little better :

#define FALSE 0
#define TRUE (!FALSE)


A better version that is totally independant from the CPU :

#define FALSE (1 == 2)
#define TRUE (!FALSE)


One thing that is always bad is a comparison with TRUE
or FALSE, I go with the K&R standards there :

if (value == TRUE) should always be replaced with
if (value)

if (value == FALSE) should always be replaced with
if (! value)


so actually there's no need for any TRUE/FALSE definition,
just drop them.


Of course this decision should influence the naming conventions
for "boolean" variables in your program. "Good" names are like
this :

HasLegalValue
IsLoggedOn
PasswordIsChecked

If you have them like this, the if() construct with or without
NOT even becomes human readable, e.g. :

if (! IsLoggedOn)
PerformLogon();



Please do not check all my sources now - I am experienced so
I don't need to follow those rules ;-)

I do follow them in all sources that I have written for
commercial customers though.



[View Quote]

Apr 11, 2004, 7:21pm

[View Quote] I don't use MFC/VC++. It worked in gcc... it may just be a compiler
only thing.

Apr 11, 2004, 7:23pm

[View Quote] > I was always under the distinct impression that the C++ rules of engagement
> so to speak defined that the actual types types true and false meant 'value
> present' or 'value not present' for false. While true is 1 for maths
> operations etc, in logic operations it is defined as 'anything not zero' so
> to speak.
>
> if (1)
> printf("The result is true\n");
> else
> printf("The result is false\n");
>
>
> - MR
>
>

Put true in the if statement then use anything not zero.

It'll still return false, if say, 927 is used.

Apr 11, 2004, 8:09pm

> I don't use MFC/VC++. It worked in gcc... it may just be a compiler
> only thing.

It's a style thing ;-)

Apr 11, 2004, 8:57pm

AW use to be on Quad T1 lines now there on OC1

http://www.activeworlds.com/products/hosting.asp

Apr 11, 2004, 10:29pm

[View Quote] That what I thought it was. :-D

Apr 11, 2004, 11:23pm

*Bowns to the ananas*

- MR

[View Quote]

1  |   Order by index