Page 2 of 2
Posted: Wed Jan 03, 2007 1:24 am
by Christopher
ole wrote:Huh?
OK I'm guessing RTQ stands for "read the question".
RTQ == Really Tricky Question
ole wrote:I suggested persistent connections. If that was incredibly stupid suggestion for some reason...well I've never used sockets before and please educate me

Sorry to confuse ... your answer was brilliant (as ever

). A quick search of the online manual for "socket" functions obviously turned up the answer.
Posted: Wed Jan 03, 2007 3:40 am
by volka
The really tricky part is to assign a particular socket connection to a particular session. Really depends on what BIGjuevos is trying to achieve.
Posted: Wed Jan 03, 2007 1:09 pm
by Weirdan
pfsockopen is not going to help really because unless you're very lucky, next request would get served by a different apache process.
Posted: Wed Jan 03, 2007 3:11 pm
by Ollie Saunders
arborint wrote:Sorry to confuse ... your answer was brilliant (as ever

).
Ahhh thanks arborint you rule too!
pfsockopen is not going to help really because unless you're very lucky, next request would get served by a different apache process.
Really? That makes them pretty useless doesn't it?
Posted: Wed Jan 03, 2007 3:24 pm
by RobertGonzalez
Weirdan wrote:pfsockopen is not going to help really because unless you're very lucky, next request would get served by a different apache process.
Does this have any relation to thread safety?
/ hangs head in apologeticness since I didn't mean to take over the thread but was really curious and didn't want to look like an inexperienced n00b asking a thread related question.
Posted: Wed Jan 03, 2007 4:07 pm
by Weirdan
Everah wrote:
Does this have any relation to thread safety?
php on its own may or may not be thread-safe (it depends on the extensions loaded/compiled in). So it's actually not valid to talk about thread-safety of one particular function when entire module could be thread-unsafe.
Posted: Wed Jan 03, 2007 4:10 pm
by Weirdan
ole wrote:
pfsockopen is not going to help really because unless you're very lucky, next request would get served by a different apache process.
Really? That makes them pretty useless doesn't it?
Well, they serve their purpose when you want both to limit the number of connection to particular service and get rid of connection instantiation overhead.