bloody outrageous prices for "Jiveforums"! my god...

[KuraFire]

Originally Posted by filburt1

I wasn't necessarily talking about XHTML compliance but 80-character-line-limits, accessibility compliancy including section 508, etc.

Queue a developer to retaliate, but I feel that my opinions are valid.

REAL accessibility starts with complete Webstandards compliance, so the architecture should be:

1) fully compliant XHTML 1.1 Trans or better;
2) fully compliant CSS and as meaningful markup as possible;
3) Section 508 compliance;
4) WCA G compliance;

Just going for 508 compliance without even so much as a doctype won't really cut the bill. Sure, it may work for screenreaders, but you cannot justifiably use the phrase "we are compliant with all accessibility requirements".

Anyhoo, I understand the difference, just didn't think about it when I made the first post

Oh, and ESPN uses a cgi-based board on the MSN Network. ;p

[colicab-d]

bulletin is not necessarily slow on large sites, theres things to consider like... is mysql on a seperate server? what kind of bandwidth is vb`s images using no tot mention any styles etc... even with the basic skin a lot of image bandwidth could be used, theres always the little niggles etc that can help speed up a forum, i mean if vb used no images and stuck to txt based or css defined buttons (u know those site that use only css type deals).

Sorry if i seem cheeky in what i say, im just eager to learn, not startin fights etc

>> Just coverin me ass lol

[KuraFire]

Originally Posted by colicab-d

(u know those site that use only css type deals).

My upcoming site will have CSS buttons instead of image buttons for virtually all buttons used on vB

It'll also be a predominantly table-less design, with innovative new approaches to forumdesigning ^_^

[Wayne Luke]

Originally Posted by AWS

Which gets upwards of 1 mil online at a time and 5000 or so posts every minute. Jive could handle this. Open Topic could handle it. The enterprise forum that ESPN uses can and does handle it. Vbulletin could not.

Actually, Disney is currently evaluating vBulletin to replace its current forum system on all its sites including ESPN because the current system cannot handle the load.

[KuraFire]

Originally Posted by Wayne Luke

Actually, Disney is currently evaluating vBulletin to replace its current forum system on all its sites including ESPN because the current system cannot handle the load.

Seriously, Wayne? Like, they've contacted you (Jelsoft) about that?

[Zachery]

Originally Posted by KuraFire

Seriously, Wayne? Like, they've contacted you (Jelsoft) about that?

That would be very awsome

[Hobbes]

Originally Posted by Wayne Luke

Actually, Disney is currently evaluating vBulletin to replace its current forum system on all its sites including ESPN because the current system cannot handle the load.

disney and espn..dude! that would pwn..

[Alien]

No, owning Disney and ESPN would pwn.

[AWS]

I like vbulletin, but, I just don't think it can handle the stress it will put under if ESPN uses it.
I don't think it will be all vbulletins fault however. Mysql wouldn't be able to handle it. Unless a port to Oracle or another more scalable db is the works.
I'd like to see them switch to a linear display forum. The threaded version they run makes it hard to follow the discussions. Yet that brings up another problem vbulletin might have if it ran there. Many threads have 1000 of more replies. Even with paganation this would put a strain on mysql.

[Dean C]

Which reminds me - what happened to the possible implementation of using another database system via vB's class?