In the Web Services world, everything is about standards to follow (web services are not just RPC). In practice, some agent (the name given to the code that implements something) implements some Interface (in the OO sense).

While designing an application server... I faced a problem... The application server I'm talking about will be composed by a "Kernel", that will receive the register requests for each "Agent" loaded by the application. Like....

# The Oak2::Kernel namespace will be populated by
# some Kernel implementation. The idea is that
# Oak2::Kernel is just an API that anyone can
# implement.
Oak2::Kernel::LocalAgentsOnly->load();

# The following code will load two agents, that will
# automatically register itself in the Kernel.
Some::Agent->load();
Another::Agent->load();
[download]

Now, let's suppose this two different agents provides the same interface... Let's say "http://www.example.com/some/interface". The question completely open is: What would be returned when the user looks up for this interface like...

# This is how it's possible to get any object
# anywhere inside the application server...
my $impl = Oak2::Kernel->lookup("http://www.example.com/some/interface
+");
[download]

So, what $impl would be?

• Nothing, Oak2::Kernel would throw an error explaining the user should use a method specifically for multi-implementation interfaces.
• A list or arrayref containing all the implementations for this interface.
• One of the two implementations, randomically selected...
• One of the two implementations, based on some rules (which kind of rules?)
• A proxy object which would propagate all messages to all implementations.

Well, all here is nothing but sketches, so any suggestion is more than wellcome, including its-all-wrong-this-way-would-be-better ones...

Hope you can meditate more than me...