> I'd argue for rate limiting as the application only gets back new data,
> never a cached value n times in a row.
No the application gets back no data, ever, because a third party application
keeps beating it. You don't even need maliciousness for this, synchronization
effects and locking on the file will ensure it gets you in the end
> With caching, you'd have to let the application know when the cached
> value was last read and how long it will be cached for. With rate
fstat() mtime. That seems easy enough
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu Jun 07 2001 - 21:00:16 EST