Re: Desperately need help with threaded socket

The requirement for the parent to be able to thread and then pass a message to the broker from a thread is non-negotiable.

There's nothing to say. You've forbidden the solution. Good luck, cos you're gonna need it.

Expanded version; You are trying to mix a badly implemented; grossly inadequate; fundamentally flawed; green threads ~~f*** up~~ implementation; with, proper, tested, functionally flawed, but functional, useful, consistent, simple-to-use, threading. You deserve what you get.

Sounds harsh, but... there is no solution to willful stupidity.

With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

"Science is about questioning the status quo. Questioning authority". I'm with torvalds on this

In the absence of evidence, opinion is indistinguishable from prejudice. Agile (and TDD) debunked

Comment on Re: Desperately need help with threaded socket

Replies are listed 'Best First'.
Re^2: Desperately need help with threaded socket by 5haun (Scribe) on Jan 21, 2015 at 00:57 UTC
Ok. Now that we have the deserved "smell the roses because it's reality" comment out of the way, are there any out-of-the-box ideas? I can think of switching to TCP messaging for one (each thread listens on its own port - slow but an option). Is there anything faster?	[reply]
Re^3: Desperately need help with threaded socket by 5haun (Scribe) on Jan 21, 2015 at 08:41 UTC
Hhmmm... Has anyone tried to do something like this using ZeroMQ? The ZeroMQ Request-Reply Broker pattern seems like it would fit my problem's requirement, particularly if I added a Queue Proxy. Each parent thread could be a client (I have control over the API the parent threads use to talk to the broker).	[reply]
A reply falls below the community's threshold of quality. You may see it by logging in.


Just another Perl shrine
	PerlMonks