search for: domstr

...plicit "track ID" into > Ogg, which will define a fixed order independent of the parsing system > and will allow us in JavaScript to directly address tracks. > > For example, the current draft looks something like this: > > interface MediaTrack { > readonly attribute DOMString title; > readonly attribute DOMString type; > readonly attribute DOMString role; > readonly attribute DOMString lang; > attribute boolean enabled; > ... > }; > interface MediaTracks { > readonly attribute unsigned long length; > getter MediaTrack item(i...

...ether we need to introduce an explicit "track ID" into Ogg, which will define a fixed order independent of the parsing system and will allow us in JavaScript to directly address tracks. For example, the current draft looks something like this: interface MediaTrack { readonly attribute DOMString title; readonly attribute DOMString type; readonly attribute DOMString role; readonly attribute DOMString lang; attribute boolean enabled; ... }; interface MediaTracks { readonly attribute unsigned long length; getter MediaTrack item(in unsigned long index); ... }; inter...

...ether we need to introduce an explicit "track ID" into Ogg, which will define a fixed order independent of the parsing system and will allow us in JavaScript to directly address tracks. For example, the current draft looks something like this: interface MediaTrack { readonly attribute DOMString title; readonly attribute DOMString type; readonly attribute DOMString role; readonly attribute DOMString lang; attribute boolean enabled; ... }; interface MediaTracks { readonly attribute unsigned long length; getter MediaTrack item(in unsigned long index); ... }; inter...

...ether we need to introduce an explicit "track ID" into Ogg, which will define a fixed order independent of the parsing system and will allow us in JavaScript to directly address tracks. For example, the current draft looks something like this: interface MediaTrack { readonly attribute DOMString title; readonly attribute DOMString type; readonly attribute DOMString role; readonly attribute DOMString lang; attribute boolean enabled; ... }; interface MediaTracks { readonly attribute unsigned long length; getter MediaTrack item(in unsigned long index); ... }; inter...

...mizing options socket options = TCP_NODELAY getwd cache = yes oplocks = yes fake oplocks = no keep alive = 30 dead time = 15 read prediction = yes ------------------------------------- Martin Geigl Universitaet Greifswald Institut fuer Physik Domstr. 10a 17489 Greifswald Tel.: +49-3834-864745 Fax: +49-3834-864701 -------------------------------------

I saw a little discussion about this a few weeks ago but nothing concrete. We're running samba-1.9.18p8 under Solaris 2.6x86. I am periodically getting the following in the logfiles, usually _many_ at a time: 1998/11/03 14:42:00 request_oplock_break: no response received to oplock break request to pid 5411 on port 40884 for dev = 1980040, inode = 33c4d When I look up the PID (in this case