[standards-jig] Disco features caching

Peter Millard me at pgmillard.com
Wed May 21 15:09:26 UTC 2003

Jacek Konieczny wrote:
[Stuff Munched]
> That is why some kind of disco reply caching should be implemented on
> server. It could be just caching of last client reply - but this will
> not work well if the feature list changes during a session. Other
> solution would be publishing the list to the server (similary to what
> can be done with disco items). The list on the server should be
> maintained for one resource and one session - I don't think persistent
> storage of this information is needed.

This seems like an implementation issue for servers which are designed to
interact with mobile clients. How would this impact protocol?? (I don't think it


More information about the Standards mailing list