Scratch

blob8108 wrote:

Magnie wrote:

Other possible plans are allowing multiple mesh networks on a single server. So someone could create their own Mesh network and people could login to that one.

This is cool!    Having multiple mesh networks is a good idea. You could broadcast "join <network>" from the client, or something similar.

Yeah, that's my plan. I'm also thinking of using a password for the networks as well (broadcast "join <network> <password>").

blob8108 wrote:

I'm also thinking of a way to close the server while it's in the background without using the 'kill' command.

I still think you should try Twisted    It handles all the connection/threading/"select" stuff for you; and I think it has built-in handling of things like shutting down the server nicely after a Ctrl-C (or you could hack it to make it do so)... (:

.... We both know I've had troubles with Twisted. It's just not something I want to use. I prefer keeping to all the default modules that come with Python.

bobbybee wrote:

I personally think that if you're doing mesh server, you shouldn't include a protocol. Only bare-old mesh. Have the VPS itself get IO commands.

The Python script above is bare-old mesh at the moment. I'll probably keep the current code and then develop another one with features (like multiple mesh networks).

How long till' you have a window's version?    I'll download Python, so I can run the un-compiled version when it's done (Or the compiled version)

DigiTechs wrote:

Magnie wrote:

Code:

#!/usr/bin/env python

I guess this is why it doesn't work on windows - since Windows doesn't use that kind of way to "manage" the place of Python.

Actually, you can still run it (it'll work fine) the only problem is that the 'select' module doesn't support windows. 

Anyways, here is the Windows Mesh Server code:

#!/usr/bin/env python

"""
This is a Mesh Server for Scratch (and possibly any project)
that you can run in the background on a VPS of the sorts.

It's totally insecure and anyone can connect and attempt to
send messages (whether broadcasts or sensor-updates) to the
users connected.

This version supports Windows! :D
"""

import select
import socket
import sys
import threading

class Server:
    def __init__(self):
        self.host = ''
        self.port = 42001
        self.backlog = 5
        self.size = 1024
        self.server = None
        self.threads = []

    def open_socket(self):
        try:
            self.server = socket.socket(socket.AF_INET,
                                        socket.SOCK_STREAM)
            self.server.bind((self.host,self.port))
            self.server.listen(5)
        except socket.error, (value,message):
            if self.server:
                self.server.close()
            print "Could not open socket: " + message
            sys.exit(1)

    def run(self):
        self.open_socket()
        running = 1
        while running:
            
            try:
                c = Client(self.server.accept())
                c.start()
                self.threads.append(c)
            
            except KeyboardInterrupt:
                junk = sys.stdin.readline()
                running = 0

        # close all threads

        self.server.close()
        for c in self.threads:
            c.join()

class Client(threading.Thread):
    def __init__(self,(client,address)):
        threading.Thread.__init__(self)
        self.client = client
        self.address = address
        self.size = 1024

    def run(self):
        running = 1
        while running:
            try:
                data = self.client.recv(self.size)
            except Exception, e:
                self.log(str(e))
                data = ''
            
            if data:
                for user in s.threads:
                    try:
                        user.client.send(data)
                    except Exception, e:
                        self.log(str(e))
            
            else:
                self.client.close()
                running = 0
    
    def log(self, string):
        try:
            log_file = open("mesh.log", 'a')
            log_file.write('\n' + string)
            log_file.close()
        except IOError, e:
            log_file = open("mesh.log", 'w')
            log_file.write(string)
            log_file.close()

if __name__ == "__main__":
    s = Server()
    s.run()

I made a quick chat client (lol) to test it out and I realized that any message you send to the server is echo'ed back to you and I was debating if that's a good thing or a bad thing but I couldn't come up with a reasonable opinion. What are your guys' opinions? Should I keep the echo or remove it?

blob8108 wrote:

Magnie wrote:

I made a quick chat client (lol) to test it out and I realized that any message you send to the server is echo'ed back to you and I was debating if that's a good thing or a bad thing but I couldn't come up with a reasonable opinion. What are your guys' opinions? Should I keep the echo or remove it?

I'd remove it; Mesh is quite slow as it is, and sending unnecessary traffic doesn't really sound like a good idea... 

Yeah, I'm also thinking to remove it as well because it can mess up scripts and stuff.

Wow, this sounds so cool! 

SJRCS_011 wrote:

So what does this do again? Does it just echo back the variable declarations across all connections?
If so, I'd be willing to make the EXE for you in C++.
And maybe I'll make a Jar as well 

Yeah, that's basically all it does.    You can make the Jar file. 

lallaway: I'll upload an EXE in the next 10 hours.

Last edited by Magnie (2012-04-27 09:56:52)

DigiTechs wrote:

SJRCS_011 wrote:

So what does this do again? Does it just echo back the variable declarations across all connections?
If so, I'd be willing to make the EXE for you in C++.
And maybe I'll make a Jar as well 

EDIT: nvm about the EXE, apparently my IDE doesn't have a built-in compiler 

Upload the solution somwhere (or source files) and i'll compile them for you, since my C++ program has a built in compiler (thanks, Microsoft)

yeah, I'm using Eclipse (for C/C++), cause I don't have admin permissions on my computer 
But Magnie has already said that the EXE will be ready within 10 hours, so we should be fine.

Last edited by SJRCS_011 (2012-04-27 10:42:00)

The Mesh Server just takes all input and sends it to everyone else connected. So technically both.

EXE-build1 can be downloaded here. 

SJRCS_011 wrote:

Here's my java alpha
On SourceForge!

Sweet! Thanks!

SJRCS_011 wrote:

Magnie wrote:

SJRCS_011 wrote:

Here's my java alpha
On SourceForge!

Sweet! Thanks!

I'll add the multiple networks later.  Gotta work on a science project.....
could you tell me if you encounter any bugs?

Okay, first bug! I can't seem to send broadcasts or sensor-updates to other clients that are connected. 

It also took me a bit to realize that it's running in the background. xD