Collection Paging

[Sean McCullough]

Sincere apologies if this has been covered elsewhere, but I could not find anything about it in the archives.   Short: How can a client find out how many entries are in a collection without fetching all of them?   Long: http://bitworking.org/projects/atom/draft-ietf-atompub-protocol-08.html#rfc.section.9.1 describes the “first”, “next”, “last” and “previous” paged request links to be included in a collection response, but doesn’t specify how to let the client know how many *total* entries exist in the collection.  With only these four links, how would one construct a set of pagination links like the list of “gooooogle” results at the bottom of a search page (or set the size of a proportional scroll bar for the list of entries in a rich client)?   -Sean McCullough