Getting pgsql people involved sounds a great idea. Having some more people
to argue for formalised and standardised database APIs like SQL, and
experience with relational operations and optimisation would be good (That
is an assumption on my part, but then they are writing PostgreSQL not
CouchDB).
Keean/Charles:
I definitely think the more people involved the better, but let's not get
too hung up on the specifics of PostgreSQL, BDB, etc. Our goal here should
be to make a great API for web developers while balancing practical
considerations like how difficult it'll be to implement and/or
Hi all,
I¹m working to develop some widget URI tests. I notice there is nothing yet
linked from the pubstatus page.
I¹ve attached a widget which performs one simple test: verify if the
window¹s location.protocol attribute is ³widget:². This was modeled upon the
widget interface tests. It passes
I have already said I have no specific concerns regarding this change. Its
difficult to predict problems that will emerge when people actually try and
use an API. That's why there are so many bad APIs out there. One way to
mitigate this risk is to look at well used existing APIs (in languages like
Hi Charles,
Le mardi 08 mars 2011 à 21:14 -0800, Charles Pritchard a écrit :
InkML is a development relevant to mobile Web.
Tablets and other input-rich devices are gaining in acceptance (and
becoming easier to purchase).
InkML is one of the few specs to put forward both a stream-based and
On Tue, 08 Mar 2011 19:47:47 +0100, Arun Ranganathan a...@mozilla.com
wrote:
Do you disagree that FileList should be a sequence parametrized type?
I think the construct of a parametrized type makes a lot of sense. But it
should work like the types we have to date, so that NodeList,
Ian, Leigh, Dimitri, All,
On March 11, the agenda of the so-called Hypertext Coordination Group
[HCG] will include XBL [XBL] to continue related discussions they had
during their Feb 11 call [Feb-11-Mins]. I wasn't present at that call
but based on those meeting minutes and what Leigh said
On 03/09/2011 04:14 PM, Arthur Barstow wrote:
Ian, Leigh, Dimitri, All,
On March 11, the agenda of the so-called Hypertext Coordination Group
[HCG] will include XBL [XBL] to continue related discussions they had
during their Feb 11 call [Feb-11-Mins]. I wasn't present at that call
but based on
Microsoft supports this.
From: public-webapps-requ...@w3.org [mailto:public-webapps-requ...@w3.org] On
Behalf Of Arthur Barstow
Sent: Wednesday, March 02, 2011 4:08 AM
To: public-webapps
Subject: CfC: publish Last Call Working Draft of Progress Events spec; deadline
March 7
Given no comments
Apologies for missing the March 7 deadline. We tried to carry out a detailed
pre-Last
Call review and have the following feedback. Microsoft would like to discuss
these
points before moving the Last Call.
Thanks,
Adrian.
Feedback on latest draft of Web Workers
Based on our understanding of
Microsoft supports this CfC.
From: public-webapps-requ...@w3.org [mailto:public-webapps-requ...@w3.org] On
Behalf Of Arthur Barstow
Sent: Thursday, March 03, 2011 5:26 AM
To: public-webapps
Cc: Mark Nottingham; Julian Reschke; Nikunj Mehta
Subject: CfC: to stop work on Programmable HTTP Caching
Adrian - the timing of your email is unfortunate. The publication
process has already started so we will consider your comments as LC
comments.
-Art Barstow
On Mar/9/2011 9:58 AM, ext Adrian Bateman wrote:
Apologies for missing the March 7 deadline. We tried to carry out a detailed
pre-Last
On 3/9/11 7:12 AM, Anne van Kesteren wrote:
On Tue, 08 Mar 2011 19:47:47 +0100, Arun Ranganathan
a...@mozilla.com wrote:
Do you disagree that FileList should be a sequence parametrized type?
I think the construct of a parametrized type makes a lot of sense. But
it should work like the types
This email is written as the position of several Chrome engineers
working in this problem area at Google, though not Google's official
position.
On Wed, Mar 9, 2011 at 6:14 AM, Arthur Barstow art.bars...@nokia.com wrote:
* What is the latest implementation status of the XBL2 CR [XBL2-CR] and
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12272
Summary: Improve section on DNS spoofing attacks to address
user attacks
Product: WebAppsWG
Version: unspecified
Platform: All
OS/Version: All
Status: NEW
On Wed, Mar 9, 2011 at 9:39 AM, Tab Atkins Jr. jackalm...@gmail.com wrote:
This email is written as the position of several Chrome engineers
working in this problem area at Google, though not Google's official
position.
On Wed, Mar 9, 2011 at 6:14 AM, Arthur Barstow art.bars...@nokia.com
On Mar 7, 2011, at 6:07 PM, Boris Zbarsky wrote:
On 3/7/11 8:55 PM, Glenn Maynard wrote:
I'd expect CanvasPixelArray to allow optimizations that ArrayBuffer
doesn't, since the implementation can use the native surface format,
translating to RGBA for the script transparently. This can matter
On Mar 7, 2011, at 7:12 PM, Glenn Maynard wrote:
On Mon, Mar 7, 2011 at 9:07 PM, Boris Zbarsky bzbar...@mit.edu wrote:
On 3/7/11 8:55 PM, Glenn Maynard wrote:
I'd expect CanvasPixelArray to allow optimizations that ArrayBuffer
doesn't, since the implementation can use the native surface
On Wed, 09 Mar 2011 15:14:48 +0100, Arthur Barstow art.bars...@nokia.com
wrote:
* Which members of WebApps want to continue with the XML-based version
of XBL2 as codified in the XBL2 CR? If you are groupin this , what firm
commitments can you make to push the spec along the REC track? Would you
On Wed, 9 Mar 2011, Arthur Barstow wrote:
* What is the latest implementation status of the XBL2 CR [XBL2-CR] and
Hixie's September 2010 version [XBL-ED] (previously referred to as
XBL2-cutdown)?
I'm not aware of any new developments on either front.
* Which members of WebApps want to
Here's my best understanding of the ansers to these questions from the
Forms WG perspective:
We continue to cheer for the development of a component system for the
HTML5 stack, as it will make things easier for end-user authors and for
framework developers, whether they choose to express
On 3/9/11 1:54 PM, Glenn Maynard wrote:
Any system with memory protection can interrupt on write, which makes
copy-on-write very close to free, as long as you can page-align the buffer.
That's a pretty serious caveat, though. And you're assuming that memory
meta-operations like set up a
On 3/9/11 1:56 PM, Anne van Kesteren wrote:
I do not think the XML-based version makes sense anymore. It's too
complex and has always felt a bit awkward. A set of extensions to HTML
or CSS would make more sense. I really quite liked the idea of using CSS
and having some way of writing markup in
Arthur Barstow:
* Should the WG pursue Dimitri Glazkov's Component Model proposal
[Component]? If yes, who is willing to commit to work on that spec?
I promised Dmitri some use cases from the SVG WG’s perspective, but
haven’t managed to get to working on these yet. Whatever solution we
have in
On Wed, Mar 9, 2011 at 3:40 PM, Boris Zbarsky bzbar...@mit.edu wrote:
On 3/9/11 1:54 PM, Glenn Maynard wrote:
Any system with memory protection can interrupt on write, which makes
copy-on-write very close to free, as long as you can page-align the
buffer.
That's a pretty serious caveat,
(off-list)
On Wed, Mar 9, 2011 at 1:25 PM, Cameron McCormack c...@mcc.id.au wrote:
svg …
star cx=100 cy=100 points=5/
/svg
svg
x-star cx=100 cy=100 points=5/
/svg
~TJ
Cameron McCormack:
svg …
star cx=100 cy=100 points=5/
/svg
Tab Atkins Jr.:
svg
x-star cx=100 cy=100 points=5/
/svg
Or that. :) I have the feeling that we don’t have agreed upon rules on
how authors are allowed to extend the platform. Whatever we deem is the
“proper” way for
Greetings, fellow Web-Platform-o-nauts,
Summary: We need a proper Isolation Model for the Web. Component Model ain't it.
Art's email prodded me to condensate some of brain ether accumulated
while looking at the use cases. Here's some for ya.
After a productive discussion with the Caja folks and
On 3/9/11 7:30 PM, Dimitri Glazkov wrote:
From the perspective of the component, the isolation is unfairly
punishing -- you can't use the outside DOM or even DOM element on
which you're hoisted, you can't add methods to it, and you have to
always imagine the membrane in order to build a proper
On 3/9/11 10:29 PM, Ryosuke Niwa wrote:
This is sort of a requirement for being able to use components that
you don't trust to arbitrarily mess with your DOM though, no?
We already have very complicated security mechanisms for frames, and the
history of the Web tells us that it's really
30 matches
Mail list logo