> If you are saving to SQL you can limit this from the SQL end as well > as the PHP code, but it's worth doing at the PHP level too.
By contraining the size of the string to "tiny" or whatever, right? I could also use Javascript, but I like that PHP is more of an invisible hand. I'm not using mySQL yet, that's the next step. Some other day. I'm using PHP to modify the original guestbook.html page, and for now because I don't expect a lot of comments, I prefer the quick access. No using PHP to access a sleepy database and finding the contents to fill the page and then display it. I just don't need that level of performance yet. Maybe when I need a second page of comments, but I don't want these comments to get carried away. It's more a luxury item to comment on an editorial written on my magazine. I'll have to get into mySQL when I start storing and saving more DB info, a catalog of some sort, saving a user's log-in and settings, but it seems like overkill for this tiny bit of functionality. I presumed that if someone ran my file.php from the server that there would be some kind of transformation to render the tags before they are displayed. I find it fascinating that just moving the file off the server to your hard drive with something like Save Target As... manages to do the same transformation. That's one of the things I don't like about Javascript... it's so open to scrutiny. -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
