On Sat, Aug 27, 2005 at 05:16:06PM -0400, Rocco Caputo wrote:
On Aug 26, 2005, at 16:27, Jeff Lowrey wrote:
use POE::Component::Server::MDP::POEQueueProvider;
Wow, that's long, and Provider seems to overlap with Server.
POE::Component::MDP::QueueProvider still has some length to it, but
it sounds a lot less redundant. I assume there will be a lot of
modules below POE::Component::MDP.
I'm happy to move up from Server.
There will in fact be several different Providers, I have two now and
will, I think, shortly do one for a Thread::Queue. So I can't really
use "QueueProvider" for the one I showed, since they will all be
queue providers. I could go with just POEProvider. But that might
be redundant... Brevity should never fall before clarity except in
the service of obfuscation. Well, maybe not never..
On Sat, Aug 27, 2005 at 05:16:06PM -0400, Rocco Caputo wrote:
Any objections to the namespace? Better suggestions?
"Perl Messaging Service" has already been rejected... ;-)
Perl Queuing Runtime Server Thingy? :)
Nahh. Then I'd have to build a UniversalVarientWorkingXample...
:-)
At 05:26 PM 8/27/2005, Erick Calder wrote:
> On Aug 26, 2005, at 16:27, Jeff Lowrey wrote:
>
>> use POE::Component::Server::MDP::POEQueueProvider;
is a server really a component? wouldn't POE::Server::MDP make more sense?
Well, I was working from Poco::Server::SimpleHTTP...
Also, I didn't want to create POE::Server myself. Happy to do it if
it seems appropriate.
At 05:38 PM 8/27/2005, Matt S Trout wrote:
POE::Server::MessageBus
POE::Component::MessageBus::Client
?
MessageBus might be a little bit reaching for me. A message bus, to
me, is more than just access to a MOM layer. It's a combination of a
MOM layer and a schema/protocol for the conversations that occur on
it. You can't do SOA without a message bus (HTTP is *not* a
messaging protocol, sorry!).
Also, I'm working from the intention that my code is acting as a
server to the user's code. So I don't want to call my code a
client. Although the whole business does get messy - as particularly
with the WebSphere MQ provider I have, my code can create both a
'server' connection and a 'client' connection (and boy that was a
pain, given the DWIM behavior of the MQSeries perl modules).
-Jeff
