Re: Avoiding option cacheing for a specific

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Re: Avoiding option cacheing for a specific

collizo4sky
‎Would love to also love to know why the option should never be cached‎.


  Original Message  
From: [hidden email]
Sent: Saturday, 20 September 2014 1:00 PM
To: [hidden email]
Reply To: [hidden email]
Subject: wp-hackers Digest, Vol 116, Issue 11

Send wp-hackers mailing list submissions to
[hidden email]

To subscribe or unsubscribe via the World Wide Web, visit
http://lists.automattic.com/mailman/listinfo/wp-hackers
or, via email, send a message with subject or body 'help' to
[hidden email]

You can reach the person managing the list at
[hidden email]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of wp-hackers digest..."


Today's Topics:

1. Avoiding option cacheing for a specific option (David Anderson)
2. Re: Avoiding option cacheing for a specific option
(Nikola Nikolov)


----------------------------------------------------------------------

Message: 1
Date: Sat, 20 Sep 2014 08:54:56 +0100
From: David Anderson <[hidden email]>
To: [hidden email]
Subject: [wp-hackers] Avoiding option cacheing for a specific option
Message-ID: <[hidden email]>
Content-Type: text/plain; charset=utf-8; format=flowed

Hi,

Where in WP core is the architecturally correct place to make sure that
a specific option is never cached?

I'm not asking about how to do this via a plugin - I'm working on a
patch to do with an issue caused by cacheing an option that would just
be better never cached.

Best wishes,
David

--
UpdraftPlus - best WordPress backups - http://updraftplus.com
WordShell - WordPress fast from the CLI - http://wordshell.net



------------------------------

Message: 2
Date: Sat, 20 Sep 2014 13:15:43 +0300
From: Nikola Nikolov <[hidden email]>
To: [hidden email]
Subject: Re: [wp-hackers] Avoiding option cacheing for a specific
option
Message-ID:
<[hidden email]>
Content-Type: text/plain; charset=UTF-8

Sorry for not being directly on topic, but why would something be
better-off not being cached? As long as you're using update_option() the
cache will be cleared when neceesary.

On Sat, Sep 20, 2014 at 10:54 AM, David Anderson <[hidden email]>
wrote:

> Hi,
>
> Where in WP core is the architecturally correct place to make sure that a
> specific option is never cached?
>
> I'm not asking about how to do this via a plugin - I'm working on a patch
> to do with an issue caused by cacheing an option that would just be better
> never cached.
>
> Best wishes,
> David
>
> --
> UpdraftPlus - best WordPress backups - http://updraftplus.com
> WordShell - WordPress fast from the CLI - http://wordshell.net
>
> _______________________________________________
> wp-hackers mailing list
> [hidden email]
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>


------------------------------

Subject: Digest Footer

_______________________________________________
wp-hackers mailing list
[hidden email]
http://lists.automattic.com/mailman/listinfo/wp-hackers


------------------------------

End of wp-hackers Digest, Vol 116, Issue 11
*******************************************
_______________________________________________
wp-hackers mailing list
[hidden email]
http://lists.automattic.com/mailman/listinfo/wp-hackers
Reply | Threaded
Open this post in threaded view
|

Re: Avoiding option cacheing for a specific

Eric Andrew Lewis
"Should never be cached" sounds like cache invalidation is your real issue.

On Saturday, September 20, 2014, <[hidden email]> wrote:

> ‎Would love to also love to know why the option should never be cached‎.
>
>
>   Original Message
> From: [hidden email] <javascript:;>
> Sent: Saturday, 20 September 2014 1:00 PM
> To: [hidden email] <javascript:;>
> Reply To: [hidden email] <javascript:;>
> Subject: wp-hackers Digest, Vol 116, Issue 11
>
> Send wp-hackers mailing list submissions to
> [hidden email] <javascript:;>
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.automattic.com/mailman/listinfo/wp-hackers
> or, via email, send a message with subject or body 'help' to
> [hidden email] <javascript:;>
>
> You can reach the person managing the list at
> [hidden email] <javascript:;>
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of wp-hackers digest..."
>
>
> Today's Topics:
>
> 1. Avoiding option cacheing for a specific option (David Anderson)
> 2. Re: Avoiding option cacheing for a specific option
> (Nikola Nikolov)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sat, 20 Sep 2014 08:54:56 +0100
> From: David Anderson <[hidden email] <javascript:;>>
> To: [hidden email] <javascript:;>
> Subject: [wp-hackers] Avoiding option cacheing for a specific option
> Message-ID: <[hidden email] <javascript:;>>
> Content-Type: text/plain; charset=utf-8; format=flowed
>
> Hi,
>
> Where in WP core is the architecturally correct place to make sure that
> a specific option is never cached?
>
> I'm not asking about how to do this via a plugin - I'm working on a
> patch to do with an issue caused by cacheing an option that would just
> be better never cached.
>
> Best wishes,
> David
>
> --
> UpdraftPlus - best WordPress backups - http://updraftplus.com
> WordShell - WordPress fast from the CLI - http://wordshell.net
>
>
>
> ------------------------------
>
> Message: 2
> Date: Sat, 20 Sep 2014 13:15:43 +0300
> From: Nikola Nikolov <[hidden email] <javascript:;>>
> To: [hidden email] <javascript:;>
> Subject: Re: [wp-hackers] Avoiding option cacheing for a specific
> option
> Message-ID:
> <[hidden email]
> <javascript:;>>
> Content-Type: text/plain; charset=UTF-8
>
> Sorry for not being directly on topic, but why would something be
> better-off not being cached? As long as you're using update_option() the
> cache will be cleared when neceesary.
>
> On Sat, Sep 20, 2014 at 10:54 AM, David Anderson <[hidden email]
> <javascript:;>>
> wrote:
>
> > Hi,
> >
> > Where in WP core is the architecturally correct place to make sure that a
> > specific option is never cached?
> >
> > I'm not asking about how to do this via a plugin - I'm working on a patch
> > to do with an issue caused by cacheing an option that would just be
> better
> > never cached.
> >
> > Best wishes,
> > David
> >
> > --
> > UpdraftPlus - best WordPress backups - http://updraftplus.com
> > WordShell - WordPress fast from the CLI - http://wordshell.net
> >
> > _______________________________________________
> > wp-hackers mailing list
> > [hidden email] <javascript:;>
> > http://lists.automattic.com/mailman/listinfo/wp-hackers
> >
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> wp-hackers mailing list
> [hidden email] <javascript:;>
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>
>
> ------------------------------
>
> End of wp-hackers Digest, Vol 116, Issue 11
> *******************************************
> _______________________________________________
> wp-hackers mailing list
> [hidden email] <javascript:;>
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>


--
Eric Andrew Lewis
ericandrewlewis.com
610.715.8560
_______________________________________________
wp-hackers mailing list
[hidden email]
http://lists.automattic.com/mailman/listinfo/wp-hackers