On Mon, Jun 29, 2015 at 7:37 AM, Vít Ondruch wrote:
> If web client had a chance to say "hey, i have a /jquery.js in the
> cache from application A with checksum 'bla', I can reuse it for
> application B, since it request /jquery.js with the same checksum".
> Actually just checking checksums coul
On Mon, Jun 29, 2015 at 6:58 AM, Stephen Gallagher wrote:
> That doesn't really help, since the main advantage to this Change
> Proposal is having a single package to update when fixes are needed,
> but nearly all web applications take pieces of jQuery out and minify
> them (taking only the parts
On Mon, Jun 29, 2015 at 4:18 AM, Stef Walter wrote:
> I think that as described, this change will cause more harm than good.
> As both an upstream and a packager of Cockpit I am against it in its
> current form.
Please note that this Change has already been implemented as approved
by FESCo for a
On Mon, Jun 29, 2015 at 04:20:11PM +0200, Reindl Harald wrote:
> a web client is not allowed to say "hey, i have a /jquery.js in the
> cache from application A and re-use it for application B" because
> that would be *easy* attack vector
If only this was possible ...
https://rwmj.wordpress.com/20
Am 29.06.2015 um 16:37 schrieb Vít Ondruch:
Dne 29.6.2015 v 16:20 Reindl Harald napsal(a):
Am 29.06.2015 um 16:13 schrieb Vít Ondruch:
That doesn't really help, since the main advantage to this Change
Proposal is having a single package to update when fixes are needed,
but nearly all web appl
Dne 29.6.2015 v 16:20 Reindl Harald napsal(a):
>
> Am 29.06.2015 um 16:13 schrieb Vít Ondruch:
>>> That doesn't really help, since the main advantage to this Change
>>> Proposal is having a single package to update when fixes are needed,
>>> but nearly all web applications take pieces of jQuery out
Am 29.06.2015 um 16:13 schrieb Vít Ondruch:
That doesn't really help, since the main advantage to this Change
Proposal is having a single package to update when fixes are needed,
but nearly all web applications take pieces of jQuery out and minify
them (taking only the parts they need in order t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Dne 29.6.2015 v 15:58 Stephen Gallagher napsal(a):
> On Mon, 2015-06-29 at 15:54 +0200, Vít Ondruch wrote:
>> Dne 29.6.2015 v 13:18 Stef Walter napsal(a):
>>> 1. How will compatibility issues be handled? In the case of
>>> Cockpit,
>>> jQuery forms
On Mon, 2015-06-29 at 15:54 +0200, Vít Ondruch wrote:
> Dne 29.6.2015 v 13:18 Stef Walter napsal(a):
> > 1. How will compatibility issues be handled? In the case of
> > Cockpit,
> > jQuery forms part of our future plugin API guarantees.
> >
> > The web application loses control of its dependencie
Dne 29.6.2015 v 13:18 Stef Walter napsal(a):
> 1. How will compatibility issues be handled? In the case of Cockpit,
> jQuery forms part of our future plugin API guarantees.
>
> The web application loses control of its dependencies, which normally
> form a intimate part of the app. How much bandwidt
On 24.06.2015 02:01, Jan Kurik wrote:
> = Proposed System Wide Change: jQuery =
> https://fedoraproject.org/wiki/Changes/jQuery
>
> Change owner(s): T.C. Hollingsworth com>
>
> jQuery is a fast, small, and feature-rich JavaScript library. It
> makes things like HTML document traversal and manip
= Proposed System Wide Change: jQuery =
https://fedoraproject.org/wiki/Changes/jQuery
Change owner(s): T.C. Hollingsworth
jQuery is a fast, small, and feature-rich JavaScript library. It makes things
like HTML document traversal and manipulation, event handling, animation, and
Ajax much simple
12 matches
Mail list logo
