Would a PHP Enterprise Advocacy Sticky Thread be Useful?

Well, this idea came up after reading the PHP Quarterly Publication thread:

http://forums.devshed.com/showthrea...&threadid=44387

I thought a nice idea would be to have a thread where people could post articles or case studies they found on the Net (or original works they create) and place them in a single thread, that way it would be a central repository for this information, instead of people having to hunt around, they could go to the thread and get a nice head start, and bring the indepth info. back to their boss quickly.

For example, this little gem was quite useful:




http://www.imakenews.com/badblue/e_article000080431.cfm

So is this a good idea? Why or why not?

Is this thread supposed to be in the PHP forums?

I think it would be Ted. I will wait to see what John says when he pops through here, and if there are enough yes's to the poll, we can make it a sticky.......

I doubt I'd ever convince my boss to use php on a large scale (we're a java shop), but maybe with some help (resources) I could get it going on some smaller stuff.

Hey cool, lots of yesses.

Some ideas so far:

1) Running list of enterprise level case studies
2) Running list of high profile sites that use PHP
3) List of enterprise level tools (application servers, IDEs, caching systems, frameworks, etc)

Oh, and of course a FAQ.

I will be glad to contribute what I can .

And there are already a couple of good threads out there on Enterprise PHP

I liked ted's one in this forum, and this one, that has a lot of goods comments from Rycamor

http://forums.devshed.com/showthrea...15&pagenumber=2

I had a go at summarising all the features that Enterprise Systems had (particularly Application Servers), that PHP wasn't supposed to have I'd be interesting in summarising this into something readable, if somebody is interested

One question I just finally understood today as I was thinking about writing a SRM banana to handle data connections, is persistent connections in PHP

(http://www.php.net/manual/en/featur...connections.php). LOL, PHP manages database resources for you already.



So providing your database is well created and you are always connecting as one user, you just need to use pg_pconnect rather than pg_connect, and you are away

Awesome,
Z

Well, it's not quite the same thing as a true connection manager. Read rod k's post near the end of the "enterprise" thread you linked above.

Persistent connections is a solution for certain situations, but it's kind of like a shotgun blast: it's possible that not all resources will hit their target. It's not true intelligent management.

We talked more about connection pooling in PostgreSQL at this thread.

So, if you are writing an SRM banana to handle PostgreSQL connection pooling/management, don't stop! It could be a Good Thing .

There are too many stickies already, IMO.

What if it was developed here, and after it got X responses, or developed to a useful level, it's moved to the PHP forum?

Not my decision...just my opinion.

---John Holmes...

Rycamor, thanks for the clariffication. Yeah I jumped to soon there, from reading those posts persistent connections aren't the same as connection pooling. I can't say I've started writing it yet, I was just writing up a simple design. I thought it might be a good first SRM project

Z.