08:49
<Zeddy>
Hey, i have everything else working in my offline webapp, except, i still haven't figured out how to reset a manifest file. The problem is i call my manifest file with parameters manifest.php?map=1, or manifest.php?map=2.. The problem is, it creates two separate caches and the amount of data stored is doubled
08:49
<Zeddy>
can i resolve this issue by using php session variables?
09:21
<SiPlus>
Hai
09:21
<SiPlus>
Any WHATWG members here?
09:21
<SiPlus>
especially websockets standard devs
09:39
<smaug____>
SiPlus: if you have questions, it is better to just ask. Someone may answer :)
09:40
<SiPlus>
Why no UDP Websockets?
09:42
<smaug____>
SiPlus: http://www.w3.org/Bugs/Public/show_bug.cgi?id=13322
09:42
<SiPlus>
smaug____, this is my post XD
09:43
<smaug____>
:)
09:43
<smaug____>
SiPlus: for websockets I'd like to see first at least one stable protocol, before adding more
09:44
<smaug____>
and also, as of now, websocket is for reliable data transfer
09:44
<SiPlus>
smaug___: is GWT Quake 2 multiplayer compatible with C source ports?
09:45
<smaug____>
I don't know what is GWT Quake
09:48
<Philip`>
Raw TCP/UDP sockets will never be allowed (because of security) - you'll only be able to talk to servers that intentionally implement WebSockets (or whatever new protocols are developed) which won't include any existing game servers
09:51
<smaug____>
(I wouldn't say 'never'. Someone may come up with reasonable permission handling ...)
09:53
<Philip`>
(That sounds like it'll always be problematic since the only person you could ask for permission is the user, and they're not going to have a clue whether they're behind a firewall and would be exposing vulnerable services)
09:55
<smaug____>
I don't know how it should work, but something like same-IP-restriction + permission
09:56
<smaug____>
SiPlus: why do you want *WebSockets* to support UDP?
09:57
<SiPlus>
smaug___: for compatibility with C-written Quake clients
09:58
<smaug____>
WebSocket API is something which runs on top of websocket protocol
09:58
<SiPlus>
Philip` Raw TCP/UDP sockets will never be allowed (because of security) - you'll only be able to talk to servers that intentionally implement WebSockets (or whatever new protocols are developed) which won't include any existing game servers
09:58
<SiPlus>
HTML5 sucks
09:58
<smaug____>
and the protocol is defined in IETF
09:58
<smaug____>
if you have problems with the protocol, you could ask IETF hybi group if they have plans to change to protocol
10:00
SiPlus
has to find a security breach to enable multiplayer in WebQuake
10:00
<SiPlus>
Are there QuakeC parsing specs?
10:01
<smaug____>
SiPlus: there is at least one thread about UDP in hybi http://www.ietf.org/mail-archive/web/hybi/current/msg02100.html
10:02
<annevk>
SiPlus, you could write an intermediary server that translates the calls from one protocol to the other
10:04
<annevk>
hsivonen, I think Opera deals with that email format fairly well, but I'm not a 100% sure
10:07
<SiPlus>
How can I draw dots in 3D space using WebGL?
10:07
<SiPlus>
no
10:07
<SiPlus>
not dots
10:07
<SiPlus>
I don't need dots
10:07
<SiPlus>
Lines
10:08
<SiPlus>
I don't see anything in my canvas
10:18
<smaug____>
Hmm, Websocket API draft points to an ancient unsafe protocol draft :/
10:28
<annevk>
it does?
10:28
<annevk>
seems to refer to the latest draft
10:37
<mhausenblas>
annevk, got a minute re CORS?
10:39
<mhausenblas>
annevk, would you think that what I've got here at http://enable-cors.org/#how-apache is correct (Header set Access-Control-Allow-Origin *)
10:40
<mhausenblas>
someone pointed out recently that it should be Header set Access-Control-Allow-Origin "*"
10:40
<mhausenblas>
with the remark: "I spent a while trying to debug this with our apache servers."
10:40
<mhausenblas>
the spec is rather clear on this, IMO
10:41
<mhausenblas>
while the Apache 2 doc not so, hence I blamed it on the doc ;)
10:41
<mhausenblas>
any advise, annevk?
10:42
<annevk>
I don't know how Apache deals with things
10:43
<annevk>
Can't you test it out on an Apache server and inspect the headers it transmits?
10:43
<mhausenblas>
well, yes, if I'd only knew which Apache version the chap is using :P
10:43
<mhausenblas>
that's what I replied him, btw
10:43
<mhausenblas>
a chap from Pixar
10:44
<annevk>
if you transmit with quotes it should fail
10:44
<mhausenblas>
but you know, I'm lazy, hence I was hoping for some advise rather than doin' it myself ... let's see
10:45
<annevk>
ah, me too ;)
10:45
<mhausenblas>
well, he claims that he has debugged it with 'their apache servers' ... whatever this means ;)
10:45
<mhausenblas>
he he, fair enough
10:45
<smaug____>
annevk: the draft has a link to http://www.whatwg.org/specs/web-socket-protocol/
10:45
<annevk>
smaug____, no it doesn't
10:45
<annevk>
smaug____, what version are you reading?
10:45
<smaug____>
http://dev.w3.org/html5/websockets/
10:46
<smaug____>
"Editor's Draft 5 August 2011"
10:46
<annevk>
oh
10:46
<annevk>
that's only in the SotD it seems
10:46
<annevk>
the actual normative references throughout the draft are to the correct version
11:11
<annevk>
smaug____, filed http://www.w3.org/Bugs/Public/show_bug.cgi?id=13700
11:26
<smaug____>
annevk: thanks
12:46
<Ms2ger>
MikeSmith, could you redirect http://dev.w3.org/2006/webapi/Binding4DOM/?
12:49
<MikeSmith>
Ms2ger: sure, what to?
12:50
<Ms2ger>
http://dev.w3.org/2006/webapi/WebIDL/
12:58
<MikeSmith>
Ms2ger: should be working now
12:59
<Ms2ger>
Works, thanks
12:59
<MikeSmith>
yup
13:20
<SiPlus>
Do WebSockets support IPX?
15:10
<eighty4>
Quick question. Would you say that "HTML5 is as different from HTML4 as coffeescript is to JavaScript" or would you just say that html5 is an evolvement of html4?
15:12
<gsnedders>
eighty4: Definitely the latter.
15:12
<eighty4>
gsnedders: thanks, was starting to think that I was completely off.
15:12
<gsnedders>
eighty4: Except I'd say evolution as a native speaker. :)
15:13
<eighty4>
meh :)
15:24
<Dashiva>
If you need an analogy, maybe say that html5 is like es3 was to earlier javascript
15:26
<Dashiva>
(although es3 had enough problems that it might not be a net positive)
15:27
<gsnedders>
Dashiva: ES5 -> ES3 is a reasonable comparison, on the whole, though
15:45
<llrcombs>
is there any way to force a <progress> to animate when its value changes?
15:45
<llrcombs>
e.g. smoothly expanding the progress bar
17:43
<Hixie>
Zeddy: why are you passing parameters to the manifest?
18:30
<Hixie>
TabAtkins: http://dev.w3.org/csswg/css3-images/ has cvs conflicts in it
19:50
<jgraham>
gsnedders, Dashiva: except that ES3 is a real spec in a way that HTML4 isn't. I mean it's not as good as ES5 but it has testable requirements an stuf
19:50
<jgraham>
*and stuff
19:51
<gsnedders>
jgraham: HTML4 has testable requirements. It's just that a desk can fulfil them.
19:52
<jgraham>
gsnedders: In that sense it is quite unlike ES3
20:31
<annevk>
gsnedders, Dashiva, except we would have defined new Date(...) completely