Queue clutter?

[raelik]

It took me a while to figure out what it was for, but I finally realized the JAVA_DYNAMIC_QUEUES that every one of my workers was "listening" on was there for the purposes of wildcard workers, and it's not a "real" queue.

Does it really make sense to tack that on the beginning of the queue list of every worker, even when said worker does have specific queues it pulls jobs from? I get why it exists for wildcards (because Resque assumes that worker names end with the queue list), but it adds a lot of clutter when I'm looking at these workers in resque-web, and it can be misleading for people who don't understand what that's there for.

Like perhaps here in createName():

jesque/src/main/java/net/greghaines/jesque/worker/WorkerImpl.java

Line 766 in 7c73e5c

.append('-').append(this.workerId).append(COLON).append(JAVA_DYNAMIC_QUEUES);

That .append(JAVA_DYNAMIC_QUEUES) call could be changed to happen only if this.queueNames.isEmpty() is true.