[wp-trac] [WordPress Trac] #31801: Use wordpress.org CDN for all hosted assets.
WordPress Trac
noreply at wordpress.org
Sun Jun 28 11:09:22 UTC 2015
#31801: Use wordpress.org CDN for all hosted assets.
--------------------------------+------------------------------
Reporter: peterwilsoncc | Owner:
Type: enhancement | Status: new
Priority: normal | Milestone: Awaiting Review
Component: External Libraries | Version:
Severity: normal | Resolution:
Keywords: | Focuses: performance
--------------------------------+------------------------------
Comment (by dorianmuthig):
Replying to [comment:6 peterwilsoncc]:
> @dorianmuthig,
>
> I can see you've posted this same comment on #26072 (related to bundling
external assets) after been directed away from #32552. A duel posting
scatter-gun approach is not going to help your cause, in fact it's going
to hinder it.
Since the issue is related, and using external resources is actually
illegal for users in all EU states, for the aforementioned reasons,
external resources are blocked or considerably slower than average in
restrictive regimes like China or the Middle East, where WordPress is a
very important tool for activists and bedroom journalists, making you
aware is a very appropriate thing.
>
> Whilst bundling assets is related, it's a slightly off-topic subject for
this ticket.
>
Your change is the wrong type of change and thus a bad change. If a change
is to be made, it should foremost be bundling. You can then opt to use a
CDN via a plugin or configuration option (the latter would need to be
added).
> My intent for this ticket as to use a single CDN - where possible - for
hosting external assets. Please keep the ticket on topic.
I am. To me, who is looking at the spot in the code affected, this **is**
the same thing.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/31801#comment:7>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list