search for: _normal_

Displaying 5 results from an estimated 5 matches for "_normal_".

2004 Mar 25
1
Packet usage
Hi again. One question: If I have an audio packet with size of (example) 35 all the bits in this packet MUSTbe read when synthesising it? Or It is normal to use only a few bits (>50%) and then get another packet?? Thanks a lot Adriano --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this list, send a message to
2014 Feb 26
0
Auto-response
Dear Sir, Thank-you for your message. I shall not be reading Yahoo Mail for quite some time. You should presume that your message remains unloved and unread. ** If you know who I am (in other words you are not a Bulk Emailer), then you already know how to contact me either on my _normal_ EMail address, or on the telephone. Yours faithfully.
2005 May 12
26
performance update
I have made additional progress with regard to performance. My latest data: configuration 1: r121.latest configuration 2: r121p.latest page c1 real c2 real c1 r/s c2 r/s c1/c2 /empty/index 6.75525 1.71983 148.0 581.5 3.93 /welcome/index 6.89044 1.89244 145.1 528.4 3.64 /rezept/index 4.99573
2006 Apr 24
9
Confusion with expressing many to many relationship
Hi folks, I am in the process of converting an existing non-rails application to rails, and am not sure what the best approach would be for specifying the relationship between the two sets of data. I''ll describe the existing table structures first. Table 1: Urls Each url has a unique id and two lists of Phrases, these are currently setup as varchars with "," delimitation -
2009 Dec 30
4
[Bug 627] New: NATed TCP-connections fail arbitrarily
....168.2.103.51602: Flags [.], ack 3972011441, win 3216, options [nop,nop,TS val 2914002455 ecr 4969985], length 1440 02:51:19.547798 IP 192.168.2.103.51602 > 62.156.238.26.80: Flags [R], seq 3972011441, win 0, length 0 Packet #1 is answered by TCP-reset-packet #2. But packet #3 is answered by a _normal_ TCP ack packet #4. Then, the subsequence packet #5 is again answered by TCP-reset-packet #6. This is also visible on the inner interface, packets #3 as well as #4 show up here again: 02:51:19.541412 IP 62.156.238.26.80 > 192.168.0.7.51602: Flags [.], ack 3972011441, win 3216, options [nop,nop...