How to write a html gui (django) for a python server module

Question

What's the way to go to build a HTML gui for eg a multiplexed tcp server in python?

I am familiar with building websites with Django, but the thing i don't understand is, how is the tcp server part communicating with the Django related views? How could i implement the data sharing (do i see the wood for the trees)? The problem for me is the mapping between the stateless "get an leave" and the "state full" py module "running as a daemon".

greetings

edit my standalone application skeleton:

#!/usr/bin/python

from django.core.management import setup_environ
import settings
setup_environ(settings)

from myapp.models import fanzy


def main():
    for each in fanzy.objects.all():
        print each.id, each.foo


if __name__ == '__main__':
    main()

I think i could import the python models into my server application. Then i could play with the api : docs.djangoproject.com/en/dev/intro/tutorial01/… Its so easy :) — enthus1ast
– enthus1ast, Commented Jul 10, 2011 at 18:25
It's not always that easy, mostly because process lifetime. For example, if you run Django through CGI with 1 request per process, then your TCP server won't stay alive between views. Similarly, if you use multiple processes to handle requests (e.g. using FastCGI), then you'll have several servers running at the same time. — André Caron
– André Caron, Commented Jul 10, 2011 at 21:04

Community · Accepted Answer · 2017-05-23 12:04:24Z

2

Django is just Python, so anything you've written in Python can be imported and referenced in the 'views' that you write for Django to serve back as HTTP responses.

In answer to another part of your question, the way a HTTP server handling TCP connections communicates with the python framework is most commonly through a protocol called WSGI. This is a good place to get more knowledge about the principles of WSGI. This is another.

With regards to running a background process and serving up a view of that processes' activities, it may be better to keep the two problems separate. You could write data to a file or a database and then access and serve this data via your web application.

These are just general comments, because your question is not totally clear. Please feel free to respond with further questions.

edited May 23, 2017 at 12:04

CommunityBot

11 silver badge

answered Jul 10, 2011 at 20:59

Gareth

1,45011 silver badges15 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

enthus1ast Over a year ago

After thinking a bit harder and reading your answers it feels naturally to write a "standard web application" with data stored in a file/db (as you sayed) then let the standalone python tcp server application work with the data stored in the db. Thats exactly what i want to do and it seems like a really beautiful way of doing it!

Community · Accepted Answer · 2020-06-20 09:12:55Z

It's not always as easy as importing the libraries, mostly because process lifetime. For example, if you run Django through CGI with 1 request per process, then your TCP server won't stay alive between views. Similarly, if you use multiple processes to handle requests (e.g. using FastCGI), then you'll have several servers running at the same time.

If you want to have permanent network connections alive independent of request lifetimes, you'll need to run the TCP server in an external (daemon) process. This is the standard procedure for some caching schemes, where all your Django processes share cached data via a single deamon (e.g. Redis).

Basically, you have two approaches.

Global connection

Either establish a connection per Django process (if you have more than one) as a global object and forward requests to this from your view. This is most convenient if your TCP server is coded to handle multiple requests per connection. However, you'll have problems if your Django process is multi-threaded.

Connection per request

If your TCP server can accept multiple short-lived connections, this is also a viable approach. Just open the connection for the lifetime of your view. If this object is used often enough, you can even add some piece of middleware that opens up the connection and stores it in the request object.

Collectives™ on Stack Overflow

How to write a html gui (django) for a python server module

2 Answers 2

1 Comment

Global connection

Connection per request

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

1 Comment

Global connection

Connection per request

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related