Do you think I could just leave this part blank and it'd be okay? We're just going to replace the whole thing with a header image anyway, right?
You are not logged in.
Offline
Thats quite cool
Although it loads a bit slow... How do you generate / send the image?
via php
its my terrible internet connection
Offline
Thanks for the cookies
Offline
destroyer123 wrote:Thats quite cool
Although it loads a bit slow... How do you generate / send the image?
via php
its my terrible internet connection
It shouldnt take that long... The images only seem to be just over 100 bytes. I guess ping might come into it though if a lot of requests are being made
Are you sure that the delays arent server side?
Edit: It seems to be faster now (less than a second instead of 2-3), maybe it was just that a lot of people were all viewing this page all at once
Offline
ninjasupeatsninja wrote:destroyer123 wrote:Thats quite cool
Although it loads a bit slow... How do you generate / send the image?
via php
its my terrible internet connection
It shouldnt take that long... The images only seem to be just over 100 bytes. I guess ping might come into it though if a lot of requests are being made
Are you sure that the delays arent server side?Edit: It seems to be faster now (less than a second instead of 2-3), maybe it was just that a lot of people were all viewing this page all at once
Propagation delay, what you here mistype as ping, is measured as the time that it takes for packets to travel through the physical wires between a client and a server.
Note: Bits travel at a speed of (2/3) the speed of light across a double twisted copper wire (i.e. 200 000 km/s).
RTT, the roundtrip time, is, instead, the time it takes for your packet to:
1) Be processed by you, the client,
2) Be dispatched
3) Be sent through the network
4) Be processed by the server
5) Do the same on the way back.
In this scenario, the transfer delay is the least of the problems.
Low bandwidth at either end (client/server)? The MTU of packets will be low regardless of propagation delay.
High service delay from the server? Clients will wait for up to seconds before timing out, propagation delay is usually in the order of magnitude of milliseconds.
Ping is instead a network utility used to test ICMP packets.
For instance, routers would usually ping other routers to test their respective RTTS during BGP routing.
Offline
I guess it isnt actually a ping message, but wouldnt the time taken to ping a message be approximately the same as the propagation delay (x2)?
Either way, what I meant was that the time for the request to be sent and routed to his server could play a part in it, as Im guessing that the connection isnt left open between images loaded, so there would be 13 * however many messages need to be sent / recieved per image (usually just one there and one back, but as he is using php idk) requests, which would mean that for about a half second load time, each request would have about a 40ms delay, which isnt too bad.
Earlier when it was 2-3 seconds im guessing that it wasnt just the delay, as it would have had to have been 200ish ms per image, which is much longer than you would expect
Offline
I guess it isnt actually a ping message, but wouldnt the time taken to ping a message be approximately the same as the propagation delay (x2)?
Either way, what I meant was that the time for the request to be sent and routed to his server could play a part in it, as Im guessing that the connection isnt left open between images loaded, so there would be 13 * however many messages need to be sent / recieved per image (usually just one there and one back, but as he is using php idk) requests, which would mean that for about a half second load time, each request would have about a 40ms delay, which isnt too bad.
Earlier when it was 2-3 seconds im guessing that it wasnt just the delay, as it would have had to have been 200ish ms per image, which is much longer than you would expect
Usually the main component of RTT is packaging/processing delay.
Where possible TCP's windowed approach will likely have sent all secondary 13 requests in parallel to the server.
Offline
3Mbps download 0.25Mbps upload
does that solve this destroyer123?
---
also what ideas do you guys think i should make with this
i think this is something really cool that could get turned into something cooler
Offline
new updateios
1) cacheing RGB images so that way it can hopefully speed up loading, tell me if you guys see a difference
2) now calling this "Color Trakk". Trakk means that it tracks your actions, it allows you to change things and different things will happen. idk i think its a good name
Offline
3Mbps download 0.25Mbps upload
does that solve this destroyer123?
250Kbps is still loads compared to the 10ish Kb of data being transferred, so I still dont think it would be (at least not completely) because of that
new updateios
1) cacheing RGB images so that way it can hopefully speed up loading, tell me if you guys see a difference
2) now calling this "Color Trakk". Trakk means that it tracks your actions, it allows you to change things and different things will happen. idk i think its a good name
much better
Offline
hey also added an api and official place for it here
read about the api to use it in your own projects if you need.
im still hungry for ideas with this, i know it can do something great.
Offline
Just thought I would add, its probably best not to use multiple cookies if you dont need to, just use one with either something like base64 for more complicated, or just a colour string for simpler things like this ("#RRGGBB" or "#RGB" with R, G and B being their hex values)
Offline
Just thought I would add, its probably best not to use multiple cookies if you dont need to, just use one with either something like base64 for more complicated, or just a colour string for simpler things like this ("#RRGGBB" or "#RGB" with R, G and B being their hex values)
Most websites would assign every user with a unique cookie identifier.
Said identifier is sent down in the TCP/IP header to the server when connecting.
Server is thus responsible to keep track of user's data, performing lookups over cookie ids.
Offline
I could use $_SESSION if it'd make you feel better. It'd be less "hackable" too.
Offline
I could use $_SESSION if it'd make you feel better. It'd be less "hackable" too.
But closing the browser will reset the color if you use $_SESSION
Offline
Just use a single cookie with red green and blue in (e.g. "#RRGGBB"), instead of using 3 cookies as you suggest you do on your website:
To save colors, Color Trakk uses cookies within the user's browsers, colr, colg, and colb
You shouldn't ever need to read / change one without changing the other two, so there isnt any point using 3 seperate cookies
Offline
[ Started around 1732674640.0102 - Generated in 0.265 seconds, 12 queries executed - Memory usage: 1.65 MiB (Peak: 1.88 MiB) ]