One possibility we're overlooking here (I'm not making any claims apart from the fact that it's a distinct solution) is to bind a run to a server on the initial exchange (e.g. do a redirect from the generic "puppetmaster pool" URL to an equivalent but more specific "the particular puppetmaster who's handling you for this run" URL). Session based web services sometimes use this technique.
-- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en.
