Forum Moderators: coopster
It was focused around web services. Now, don't get me wrong, web services are useful, I just don't care about them.
So, I met a few guys from Zend, listened to a couple of the presentations and was more than satisfied with the experience. I think it was only 40 CAD and was worth every penny and more. I had to leave early since I, unfortunately, had to get some work done before the weekend but just hearing Rasmus Lerdorf give the keynote on Pragmatic PHP was worth it, if nothing else.
you can see for yourself here
[talks.php.net...]
Overall there were some good tidbits and it was well worth the $50. Don't think I'll attend the one in three months on Security, looks too technical for me. I'm more of a marketer, I've got guys to do the hardcore stuff for me, I'll send one of them.
Nice to meet you there.
"The greatest inefficiencies come from solving problems you will never have."
- so true.
I don't know how many hundreds of lines of junk some of my stuff has to pass through just because I thought, "wouldn't it be neat if this could do that if I later need to do the other thing?" When I never end up doing the other thing.
However, if you can come up with a generalized solution that will accommodate *lots* of likely scenarios, since it's generalized, it's likely to be fast too.
"Dumb things
Don't do dumb things! "
Will always be relevant, have to keep reminding myself this.
"Try to limit yourself to 5 or less includes per request"
Funny, now that I see this, and see the opcode cache advice, I wonder if I already read a 'preview' of this lecture (think I saw a link to it from phparchitect).
You don't see this advice very often, and not many big scripts follow it. Some scripts I have installed so I can throw stuff at them show: pbpBB2 includes 14 files (including index.php, total 156K); phpnuke includes 18, 136K. I think the advice is good in general; if you have fairly advanced scripts, though, it'll be very hard to keep your code modular with only 4 or 5 includes. But limiting the number of includes as possible is very good advice - php programmers are also picking up on it slowly - the *nuke family used to include all sideblocks, whether displayed or not, about 20 or so - xaraya used to run through some included file about 15 times iirc - these aps don't do this any more iiac.
For those not familiar with it, [talks.php.net...] is a great resource - many 'talks' not so newbie-friendly since you only get the slides and not the 'talk', but indespensible if you're into exploring php.
Overall not a bad turnout, if Nathan can keep it going regularily I'm sure the momentium will grow. Lots of familiar faces there, but lots missing as well.
loading things into shared memory was the thing that myself and the sysadmin here have talked about which was very good to see in practice.
I always preach 'pragmatic php' and sometimes worry that I might be giving people bad advice so it was very reassuring to see Rasmus say the same thing. We spend a lot of time distributing the load of what needs to be done between apache/os/php etc. I seldom see people talking much about it though so seeing it mentioned there was also very nice.
"Try to limit yourself to 5 or less includes per request"
loading things into shared memoryI am doing this with all user sessions IDs, very easy+fast with mmcache_put(key, value)
but why make it necessary in the first place?
