14
Hi
@mcnaz
Okay, let´s discuss it ;)
I think we both know the difference between compiled and interpreted language, about MSIL and Bytecode, JIT and stuff. So let´s not get stuck in that discussion.
In php, you don´t have a compiler who says: in line 123, there is a datatype conversion error. in line 456, the called function is not declared. we both know.
I have written a module named webmusic, which uses a class named Category. Now it is named WebmusicCategory, because yesterday *bang* a naming conflict with a class Category in CBB occured. Such things happen if there is no compiler (okay, you could solve it with namespaces, but I nevertheless, I hope you see the point -> runtime errors instead of compile-time errors)
okay so if homerecording.de gets the double size:
When I speak of mssql, i don´t focus on speed, i mean foreign key constraints, stored procedures, triggers, transactions. Everything to guarantee data integrity in a complex environment. my page ain´t that complex that i would need such things. and MySQL is okay ans stable, with 4.1 we will be able to change for example uids in a simple way with the help of foreign key constraints, this is a big step ahead for us because we need that for merging to platforms together. okay, but it i had a even bigger and more complex site, i should have the money to host a webgarden or webfarm . as this is not the fact at the moment, I hope to gain some performance in the core hacks I´m planning now.
But generally, I see some boundaries in the complexity of php(mysql applications. I see the typical XOOPS problem, that with every hack, there is a new problem anywhere else.
So I am afraid, that someday, we have a xoosphere that is so complex that you need weeks to find a simple bug, because in line 1234, the serializer made a wrong unicode conversion. So a week later, a user complains about a smilie not showing correctly.
And I am afraid that it will make XOOPS slower. We will have more queries, we will have a load of class includes which need to be parsed. As in php, with every request objects need to be newly created (or did I miss a new application cache in php5?), this could be time-consuming. You could use serialisation to make this faster, but this could lead to new problems, or you need more code to validate the deserialisation process.
I hope I am just a stupid sceptic who hasn´t understood the concept. But at the moment, i am a bit pessimistic about xoosphere.
@phpbbb
I have sent you the class.forumpost.php. It is rather a dirty hack which writes the sanitized text to an extra column in the newbb_posts_text table. so at every display, XOOPS doesn´t have to do the sanitizing process again.
greetings
birdseedmusic
