> One solution to fix this is to have the default timeout actually be > specified by a feed;
Let me make sure I understand... I think you're saying that (for instance) the link tag would have some specification for when to check back again. I think that's a good idea. That way the provider of the feed can specify how frequently they can handle updates. If you have a default along the lines of every day or week, and you have a way to manually refresh, then it seems like all the bases would be covered. In development the provider sets the refresh to fast or every time; in production the feeds probably won't be changing much so a longer update cycle seems fine to me. > Another solution that could be used in combination with others is to > track the frequency at which the user actually uses commands from a > particular feed; this way, if the user rarely uses a particular feed, > it won't get checked very often. To me this seems less preferable. It's more complicated and I don't really see the benefit so much. I think if a user needs to drive the update they can click a link to make it happen (or use an update feeds command). Thanks for your help! - Simon --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "ubiquity-firefox" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/ubiquity-firefox?hl=en -~----------~----~----~----~------~----~------~--~---
