Hi - can any one explain to me the difference between these products and where I can get more info on UBB.x & OpenTopic.

Also can someone elaborate what the following means:

The UBB.x™ and OpenTopic™ applications use XML to organize information within the database. The end-result is that the data can be readily used in other formats.

- thanks, Naz

P.S: also the pricing info on UBB.x & OpenTopic

Um, OpenTopic has been discontinued for several years now. UBB.x is now part of the Eve Community platform, which is now only limited to enterprise purchases.

UBB.threads is a downloadable forum solutition written in PHP. It is the most reliable forum software package out there. The price is definately worth it over other paid forum packages such as vBulletin or Invision Power Board.

Wow. Well done, Pink.

I still have UBB classic. I have 6.7.1, I think it got up to .3 as the last upgrade. I'm not sure why I didn't do the last available upgrade. I know each time they had a default of 8 graemlins per post and I wanted 15, but it was never a CP feature so I got tired of looking for the file to change it manually each time there was an upgrade. Also at some point in the upgrade process UBB classic became really server intensive in terms of resources and some host providers banned it for that reason. I had to end up going to a high volume server.

Anyway, I've used UBB classic since 1999, so I've definitely been a loyal customer. I'd guess my question is how resource heavy is threads compared to classic? I'm interested in upgrading to threads, but I'd like to know that first.

I had been running classic since god knows how long and moved over to threads when 7 came out and I couldn't be happier; the resource usage dwindled to near nothingness as compared to classic...

I too have been using since '99 (I think.) I really didn't want to move from Classic but I was forced into it due to the poor performance I was getting.

COULDN'T BE HAPPIER

Make the move - it's a good move!

We made the move in 2003 since classic couldn't handle the load.

We are growing and growing, and threads is still handling the load perfectly

i've worked on threads sites with over 1million users.. no probs

also sites with over 2.5 millon posts.. some probs only in search times, but there are ways to speed that up too

Biggest differences in terms of underlying foundation are that .classic uses perl only in CGI binary mode, not built into the server like mod_perl would be. Threads, on the other hand, uses PHP which most often is built into the server. It can be run as a CGI binary mode, but usually is not. That difference is huge. If .classic was built to run mod_perl it would have been easier on the server, but not at all portable.

Next, because .classic also was built to be incredibly portable, this it was built on flat text files. It had to load many files as data, more in later versions as it got more features. Some of those text files got quite large and could get corrupted if the server was overwhelmed with too much I/O. Part of what made the later versions of .classic feel slow and heavy was all the work that was put into it to prevent data corruption.

Threads is built on a MySQL relational database which is faster and easier on the server as you scale. It's less likely to corrupt as well. It still can have it's corruption or index problems, but is less likely to have them. MySQL can also be tricky to tune as your site gets larger, but it is able to be tuned pretty easily, where a flat file system really can't without some major voodoo and with less positive effect.

So what does the VP of the parent company do in his off time? Help perspective new customers! Nice! I knew this was a great company.