We have about 3 dozen PM3s temporarily assigned dummy filters for its
users. This is causing _heavy_ load on the choicnet-servers due to a
lot requests.
Some time ago there has been a thread concerning the choicenet-PM
filter cachings.
> We're investigating alternative methods of caching the filter,
> perhaps
> by allowing the administrator to specify a time-to-live for the
> filter,
> so admins who want the filter fetched each time can do so, and
> admins
> who aren't planning to ever change the filter can cache it as long
> as
> any user is still using it, for long periods. I'd be interested in
> hearing your thoughts on the matter.
Any progress since?
For explanation, the current caching goes like this:
The first user logs in, filter is downloaded from the choicenet-server
and applied to the port. Second user with the same filter logs in, the PM
looks in his table, finds a filter with the same name and applies it to the
second port. a.s.o. But when the first user with the same filter logs
out, the filter is discarded from the PM. But it can.t be really discarded
cause other ports are still using the filter. Neverless the PM has to
download the filter once again when it is requested (eg. the next
user logs in).
-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Thomas Fennes Technical Operations EUnet EDV DienstleistungsGmbH T.Fennes@Austria.EU.net Austria.s finest IP-Provider Fon: +43 1 89933-0 Fax: +43 1 89933-533 Diefenbachg. 35 A-1150 Wien - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe portmaster-users' in the body of the message. Searchable list archive: <URL:http://www.livingston.com/Tech/archive/>