Author Topic: RTB Dedicated Hosting Service  (Read 92621 times)


So why in a zip, instead of a regular plain-text file? The only reason I can see for providing it in a zip would be to allow the user to download them all in one go, but that doesn't seem to be the intention either.

Console logs can grow fairly large and they compress well, so it makes sense to zip it to save our bandwidth and the end user's too.

Are there a set of ports open for TCP connections for Blockland server use?

Yes there will be a number of ports open for use on your server - details on that will be available later on.

Console logs can grow fairly large and they compress well, so it makes sense to zip it to save our bandwidth and the end user's too.
HTTP-level gzip...?

HTTP-level gzip...?
Zipping is the easiest way to do it for our setup and allows more efficient storage as well as more efficient transfer. Regardless, the format of log downloads is vastly insignificant and is something we definitely have under control.

Sorry, we chose to do it this way and I still think it makes sense. I don't think it's going to be an issue for our users but feel free to make your own hosting service without zipped console logs though.

Zipping is the easiest way to do it for our setup.
Sounds like something is very wrong with your setup then.

Not sure how you come to that conclusion but ok.

Sounds like something is very wrong with your setup then.

Oh stop nitpicking. There's nothing wrong with zipping.

Oh stop nitpicking.

It's exactly what lub has been doing to kalphiter's service for the last few months.

It's exactly what lub has been doing to kalphiter's service for the last few months.
With respect, you're wrong. I don't want to start the drama here, but PM me if you want to dispute this and I'll explain.

Not sure how you come to that conclusion but ok.
Pretty much every major HTTP server today has drop-in compression either built-in (for example, IIS, node.js (sure, you shouldn't run this directly against the internet anyway, but you seem to love it so)), or as a readily available module (for example, nginx, Apache2). If it's hard for your setup then it sounds like you're either incompetent and don't know how to set it up (and are too lazy to look it up), or that you decided to do something very stupid.

Since we're storing a lot of console logs we'd prefer to keep them in a compressed format on the server to use up less space. It'll also reduce the load on the webserver having to compress the files.

To be honest it does make perfect sense in this situation and I'm sorry you feel it's something to make such a fuss out of.

With respect, you're wrong. I don't want to start the drama here, but PM me if you want to dispute this and I'll explain.

Are you for real?

The majority of your posts in kalphiter's topic were designed to create drama. And don't say they were not. If you would have made a single post outlining the issues with this service then I could understand, but you seemed to have an unyielding love of repeating yourself knowing you would get a reaction.

Are you for real?

The majority of your posts in kalphiter's topic were designed to create drama. And don't say they were not. If you would have made a single post outlining the issues with this service then I could understand, but you seemed to have an unyielding love of repeating yourself knowing you would get a reaction.
This.  So much this.

I personally don't have a problem with this hosting service other than it looks fantastic but we have no numbers to prove this is fantastic.

This.  So much this.

I personally don't have a problem with this hosting service other than it looks fantastic but we have no numbers to prove this is fantastic.
Agreed! Before some people buy this service first we want to see the actual data on how its better then kalps. If the connection is about the same then I will just hope for better prices then his service.