Author Topic: Syerjchep --- img2brick soon --- quick rate --- tracking --- more stuff!  (Read 21037 times)

The domain name makes no sense to me.

The domain name makes no sense to me.
What's so hard to understand about it?
".org" is a common domain suffix.

Also, someone just tried to make a 3x6x0 brick.
Obviously if you specify non-number size arguments, or numbers less than 1 then the brick won't work.

I was not referring to the domain suffix. I mean the site name which appears to be "syerjchep" which looks like random keyboard mash to me.

True, but I've already made the webserver.
And it worked fine up and till the last update.
Now I need to find out what's causing the crashes.
Thing is, your webserver is crap.
Seriously.
I was about to test loading the homepage to check the speed.
First time without chrome dev tools open, it loads fine.
Second time, with chrome dev tools, I just can't get any response.
Third time, still with chrome dev tools, it loads just fine, again.
After that, same as second time, every time.

Edit: seems to work again now.
Edit 2: broken again.
Edit 3: see first edit.
« Last Edit: April 22, 2011, 06:00:18 PM by DontCare4Free »

I was not referring to the domain suffix. I mean the site name which appears to be "syerjchep" which looks like random keyboard mash to me.
It's been the name of my/our group/clan for many months here on Blockland, and elsewhere for even longer.
Thing is, your webserver is crap.
Seriously.
I was about to test loading the homepage to check the speed.
First time without chrome dev tools open, it loads fine.
Second time, with chrome dev tools, I just can't get any response.
Third time, still with chrome dev tools, it loads just fine, again.
After that, same as second time, every time.

Edit: seems to work again now.
I just updated it, it's gonna be faulty.
If you can't get a response, it either crashed, or is being updated.

If you can't get a response, it either crashed, or is being updated.
Now that I it seems to work again, I see that you do nothing to simplify caching.
In response to this:
Code: [Select]
Accept:application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Charset:ISO-8859-1,utf-8;q=0.7,*;q=0.3
Accept-Encoding:gzip,deflate,sdch
Accept-Language:en-US,en;q=0.8,sv;q=0.6
Connection:keep-alive
Host:syerjchep.org
Referer:http://syerjchep.org/requestlog.html
User-Agent:Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16
You send me this:
Code: [Select]
Connection:close
Content-Length:287
Content-Type:text/html; charset=UTF-8
Some whitespace got cut off when copy-pasting.
Still though, you don't send anything related to caching, and you don't compress the output.
That, for example, is why you should let someone else do the heavy http lifting for you, instead of trying to reinvent the wheel.

I was making thw wheel! No fair.
Idea steeler.

It's been the name of my/our group/clan for many months here on Blockland, and elsewhere for even longer.
I see. Looks like keyboard mash to me.

Now that I it seems to work again, I see that you do nothing to simplify caching.
In response to this:
Code: [Select]
Accept:application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Charset:ISO-8859-1,utf-8;q=0.7,*;q=0.3
Accept-Encoding:gzip,deflate,sdch
Accept-Language:en-US,en;q=0.8,sv;q=0.6
Connection:keep-alive
Host:syerjchep.org
Referer:http://syerjchep.org/requestlog.html
User-Agent:Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16
You send me this:
Code: [Select]
Connection:close
Content-Length:287
Content-Type:text/html; charset=UTF-8
Some whitespace got cut off when copy-pasting.
Still though, you don't send anything related to caching, and you don't compress the output.
That, for example, is why you should let someone else do the heavy http lifting for you, instead of trying to reinvent the wheel.
I know all about that, compression is going to be further in the future simply because the files being transferred at this point are incredibly small, and mostly text, so the compression ratio will be awefully low, and it would take a decent amount of work to do for such a little payoff. As for cacheing, the pages at this point are quite volatile, and once again, small, so while I may implement it sooner, as in tomarrow, it is still not a high priority.
I see. Looks like keyboard mash to me.
Good for you.

I know all about that, compression is going to be further in the future simply because the files being transferred at this point are incredibly small, and mostly text, so the compression ratio will be awefully low, and it would take a decent amount of work to do for such a little payoff. As for cacheing, the pages at this point are quite volatile, and once again, small, so while I may implement it sooner, as in tomarrow, it is still not a high priority.
But once again, using a finished and widely used web server would do most of this for you, and it would probably both be more secure and less effort on your part too to integrate it than to reinvent the wheel.

But once again, using a finished and widely used web server would do most of this for you, and it would probably both be more secure and less effort on your part too to integrate it than to reinvent the wheel.
Trust me, while there might be bugs to be fixed, and standard features to be added, I'm capible of doing so.
I don't know if this is easier or harder, but either way, I've already gotten a good start.

Tom

I'm on DontCare4Free's side of this. Developing your own web server may be fun, but it would be a lot of work to get the whole HTTP protocol. You probably shouldn't actually deploy it on a real site, even if it is just something for Blockland.

I'm on DontCare4Free's side of this. Developing your own web server may be fun, but it would be a lot of work to get the whole HTTP protocol. You probably shouldn't actually deploy it on a real site, even if it is just something for Blockland.
The basics of the HTTP protcol are not particularly complicated, I've read quite a bit of documentation and know how it works, including features I have yet to add and whats lack of probably form the basis of your judgement.

edit: Also, do you have anything in particular in mind when you say the "whole http protocol" as opposed to what parts of it I have implemented?

I added an accounts system, while I can make things like a rating blocklanders system without accounts, I feel that some of the more advanced features will require such a system.
However, when you register an account, the website generates a password for you, so maybe Ephailtes could awnser for me...
Would links to a website with accounts/registering be okay if the user can't possibly set their password themselves?

I tried making a 0x0x0