Areas in queues

Some queues are divided into areas in version 1.
(These areas simply provide a mechanism to narrow searches and to group requests into categories. Before defining an area, it would be wise to consider creating a new queue, particularly if requests in a certain area should be handled in any way different to requests in the main queue.) Why this opportunity is absent in version 2.0.6?
Konstantin Chekushin mailto: koch@lmt.lv
Latvian Mobile Phone Company http://www.lmt.lv
Network Support and Information Technology Group +371 7773606
+371 9248521 (mobile)

I’m sure someone will correct me if I’m wrong, but I believe the
Keyword mechanism in RT2 was intended to replace and enhance the
functionality of “Area” from RT1.

Matt Disney

“Konstantin Chekushin” writes:

This is a multi-part message in MIME format.

------=_NextPart_000_00CC_01C141EE.08CA92C0
Content-Type: text/plain;
charset=“windows-1251”
Content-Transfer-Encoding: quoted-printable

Some queues are divided into areas in version 1.=20
(These areas simply provide a mechanism to narrow searches and to group =
requests into categories. Before defining an area, it would be wise to =
consider creating a new queue, particularly if requests in a certain =
area should be handled in any way different to requests in the main =
queue.) Why this opportunity is absent in version 2.0.6?=20
–=20
Konstantin Chekushin mailto: koch@lmt.lv
Latvian Mobile Phone Company http://www.lmt.lv
Network Support and Information Technology Group +371 7773606
=
+371 9248521 (mobile)

------=_NextPart_000_00CC_01C141EE.08CA92C0
Content-Type: text/html;
charset=“windows-1251”
Content-Transfer-Encoding: quoted-printable

Some queues are = divided into=20 areas in version 1.
(These areas simply provide a mechanism to narrow = searches and=20 to group requests into categories. Before defining an area, it would be = wise to=20 consider creating a new queue, particularly if = requests in a=20 certain area should be handled in any way different to requests in the = main=20 queue.) Why this opportunity is absent in version 2.0.6?
--
Konstantin=20 Chekushin          &nbs= p;           &nbsp= ;   =20

mailto: <A href=3D"mailto:koch@lmt.lv">koch@lmt.lv
Latvian Mobile =