Hi, On Sat, May 18, 2013 at 11:13 PM, Roger Bell_West <[email protected]> wrote: > On Thu, May 16, 2013 at 12:05:14PM +0100, Roger Bell_West wrote: >>This problem is still going on. If the equeue has the id "request", it >>includes the .alive, .all, .metadata, .on_air, .resolving and .trace >>commands in the telnet interface; otherwise, it doesn't. It doesn't >>matter what order I define the queues in, or what else I name them - >>only id="request" seems to work. Can anyone account for this? > > If anyone else finds this problem: it's possible to use > request.metadata to retrieve metadata for an RID in the other queue.
Glad you solved your problem. Actually, if you named the "request" queue something else, you would still have reqest.metadata: the "request" name here does not really correspond to your id but is hardcoded. Queues only provide functions to get the rid, if you want the metadata you can simply do request.metadata rid, as you found out! ++ Sam. ------------------------------------------------------------------------------ Try New Relic Now & We'll Send You this Cool Shirt New Relic is the only SaaS-based application performance monitoring service that delivers powerful full stack analytics. Optimize and monitor your browser, app, & servers with just a few lines of code. Try New Relic and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may _______________________________________________ Savonet-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/savonet-users
