I'm looking into a fun problem at my new job at an internet registrar. We have data connections with each registry (for domain creation, transfer notification etc) that take a while to initiate - sometimes querying a domain name can take upwards of 30 seconds to cycle through all the registries.

Ideally we'd like to drop an RPC server in between the calling scripts and the registry modules, that accepts incoming requests from clients, uses an existing connection handle for the current transaction, and then passes the reply back. My first stop was with ResourcePool and Frontier::Daemon::Forking, before I realised that when the child process exits, all the connections will be shutdown when the registry objects are DESTROYed, and the next time a client connects each registry connection will have to be re-initialised, nicely eating up any speed increases already gained. My next thought was to do the registry side with non-blocking IO, but the problem here is that I can't handle those sockets directly, I need to call a method in of the existing classes and let that parse the data from the socket.

POE, specifically POE::Component::Generic::Object, looks like it might be the right way to go - specifically, the yield method. Event might also be worth checking. Ideas? This seems like a fairly solvable problem, but I'm not sure which path is the right one to take.