Author Topic: Remote Admin (server version 0.7 client version 0.8)  (Read 12247 times)

Why can't you have the thing connect to your webserver instead so you don't need to port forward for it?
Thats planned.
How long would it take to get a  web  version?
Ill make it over the weekend.

Alright, so I'm working on the web interface.
I updated the webserver to allow connections to other servers, and tried to start scripting something, but trying to make purely HTML client is quite difficult. But I don't wanna use a java applet because of two things. First, it may not show up well on all mobile devices, second, many computers in schools, libaries, other public places, block any connections not on port 80, which means it wont work.

(The idea here is that you'd probably be using this from a public computer or a mobile device, since it makes no sence to use it from a computer that can play blockland)

If the backend to this uses raw TCP sockets you won't be able to do it in HTML/JS, you'll need to use something else (Websockets/JSONP/XHR long poll - Socket.IO does it all) and bridge to a TCP server.

If the backend to this uses raw TCP sockets you won't be able to do it in HTML/JS, you'll need to use something else (Websockets/JSONP/XHR long poll - Socket.IO does it all) and bridge to a TCP server.
Obviously HTTP alone doesn't have the ability to do that. I said, HTML.
The connections are being made by the server, which is a program I wrote myself. The scripting language the pages use is LUA. (just like conventional servers use PHP)

Also, I said a java applet, not java script.

The issues here mostly deal with the fact that the add-on, and any program/applet would be constantly updating and have its own memory. Whereas a webpage only updates when the person refreshes it, and any 'memory' would have to use cookies or sessionstates to be useable.


It'd be easier for me to make a client from scratch in C++.

But that's obviously not of much use.
« Last Edit: May 09, 2013, 01:21:31 PM by DrenDran »

The issues here mostly deal with the fact that the add-on, and any program/applet would be constantly updating and have its own memory. Whereas a webpage only updates when the person refreshes it, and any 'memory' would have to use cookies or sessionstates to be useable.
So just stream to the web page so you don't need to refresh it, simple.

So just stream to the web page so you don't need to refresh it, simple.
Stream it?
I'm just using basic HTTP and HTML here, not sure what you're referring to.

Stream it?
I'm just using basic HTTP and HTML here, not sure what you're referring to.
Put Javascript on the HTML page and then...

...use something else (Websockets/JSONP/XHR long poll - Socket.IO does it all) and bridge to a TCP server.

Put Javascript on the HTML page and then...
See now I don't know what those things are, but if they're anything serverside, my webserver doesn't support them.

Basically I got lua scripts that execute whenever a page is loaded, much like PHP.
The lua has four TCP functions I programmed into it:
connect(ip,port) --- returns the socket, or -1 if it couldnt connect
send(socket,packet) --- returns the length sent
recv(socket,max) --- returns the amount received and the packet
close(socket) --- clears the socket

Keep in mind that while a connection will stay open between page viewings, my only chance to receive or send any information is while a user is requesting a page.

Create a page on your server to return raw data when it's requested, then write some Javascript to periodically query that page and update the data on your page using the data returned. RTB hosting does this a lot - periodic requests to refresh data on server dashboard and streaming using Socket.IO for the activity stream, console and server chat.

If you're up for learning something new it's all nice stuff to learn, let me know and I can point you in the right direction.

This is amazing
also 2000 post

No one is bright enough to port forward thanks to upnp.

Set the default port to 28000.

Just a thanks to Lugnut for pming me about a possible problem.

Set the default port to 28000.
have you done this yet

have you done this yet

Change log:

Version 0.7 Server
Patched a vulnerability
Set default port to 28000