Honza Bambas wrote:
The old API talks only to the old cache. It's now used for appcache
(Offline Application Cache) only.
The old API doesn't emulate the new API well enough; it actually ignores
failures to call onCacheEntryCheck, and reads uninitialised memory in
that case.
--
Warning: M
On 02/21/2014 12:01 AM, Honza Bambas wrote:
On 2/20/2014 10:25 PM, Neil wrote:
Well, that was confusing.
The old contract ID was @mozilla.org/network/cache-service;1
The new contract ID is @mozilla.org/netwerk/cache-storage-service;1
Turns out that there are two differences, not one.
Yes, forg
On 2/20/2014 10:25 PM, Neil wrote:
Well, that was confusing.
The old contract ID was @mozilla.org/network/cache-service;1
The new contract ID is @mozilla.org/netwerk/cache-storage-service;1
Turns out that there are two differences, not one.
Yes, forgot to mention, sorry. Hoped it's obvious from
Well, that was confusing.
The old contract ID was @mozilla.org/network/cache-service;1
The new contract ID is @mozilla.org/netwerk/cache-storage-service;1
Turns out that there are two differences, not one.
--
Warning: May contain traces of nuts.
___
dev
On 2/20/2014 7:01 PM, Neil wrote:
Honza Bambas wrote:
On 2/19/2014 11:25 PM, Neil wrote:
In particular, the API calls I'm interested in:
1. Given an HTTP or FTP URI, return the size of the cached data
How do you do that now? Only way known to me (with the old cache is
visit of a cache
Honza Bambas wrote:
On 2/19/2014 11:25 PM, Neil wrote:
In particular, the API calls I'm interested in:
1. Given an HTTP or FTP URI, return the size of the cached data
How do you do that now? Only way known to me (with the old cache is
visit of a cache device). We don't have devices now
On 2/19/2014 11:25 PM, Neil wrote:
Is the conversion straightforward?
The API is mostly similar, we've took it more as a chance for a cleanup
since some modification were necessary anyway.
In particular, the API calls I'm interested in:
1. Given an HTTP or FTP URI, return the size of the
Jason Duell schrieb:
Is there something specific you're wondering about?
Neil is the code module owner for SeaMonkey, I guess that might be where
he's coming from with the question - he probably wants to make sure it
still works in the future... ;-)
KaiRo
__
On Tue, Feb 18, 2014 at 7:56 PM, Neil <mailto:n...@parkwaycc.co.uk>> wrote:
Where can I find documentation for the new necko cache? So far
I've only turned up some draft planning documents. In particular,
I understand that there is a preference to toggle the cache.
Michal Novotny wrote:
On 02/19/2014 11:50 AM, Dao wrote:
On 19.02.2014 01:56, Neil wrote:
In particular, I understand that there is a preference to toggle the
cache. What does application code have to do in order to work with
whichever cache has been enabled?
Nothing? It's a different bac
On 2/19/2014 11:09 PM, Neil wrote:
Honza Bambas wrote:
On 2/19/2014 1:56 AM, Neil wrote:
Where can I find documentation for the new necko cache? So far I've
only turned up some draft planning documents. In particular, I
understand that there is a preference to toggle the cache. What
Honza Bambas wrote:
On 2/19/2014 1:56 AM, Neil wrote:
Where can I find documentation for the new necko cache? So far I've
only turned up some draft planning documents. In particular, I
understand that there is a preference to toggle the cache. What does
application code have to do in
On 2/19/2014 1:56 AM, Neil wrote:
Where can I find documentation for the new necko cache? So far I've
only turned up some draft planning documents. In particular, I
understand that there is a preference to toggle the cache. What does
application code have to do in order to work with whic
On 02/19/2014 11:50 AM, Dao wrote:
On 19.02.2014 01:56, Neil wrote:
In particular, I understand
that there is a preference to toggle the cache. What does application
code have to do in order to work with whichever cache has been enabled?
Nothing? It's a different backend behind the same API, a
+cc
On Tue, Feb 18, 2014 at 7:56 PM, Neil wrote:
> Where can I find documentation for the new necko cache? So far I've only
> turned up some draft planning documents. In particular, I understand that
> there is a preference to toggle the cache. What does application code have
&g
On 19.02.2014 01:56, Neil wrote:
In particular, I understand
that there is a preference to toggle the cache. What does application
code have to do in order to work with whichever cache has been enabled?
Nothing? It's a different backend behind the same API, at least that's
my rough and possibl
Where can I find documentation for the new necko cache? So far I've only
turned up some draft planning documents. In particular, I understand
that there is a preference to toggle the cache. What does application
code have to do in order to work with whichever cache has been en
17 matches
Mail list logo