[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnumed-devel] GNUmed web interface - technologies
From: |
Sebastian Hilbert |
Subject: |
Re: [Gnumed-devel] GNUmed web interface - technologies |
Date: |
Mon, 12 Jul 2010 07:33:38 +0200 |
User-agent: |
KMail/1.13.3 (Linux/2.6.33-6-desktop; KDE/4.4.5; i686; ; ) |
Am Sonntag 11 Juli 2010, 23:54:52 schrieb Karsten Hilbert:
> On Sun, Jul 11, 2010 at 06:37:52PM +0200, Hilbert, Sebastian wrote:
> > I am no expert on this. I currently fail to see the problem. How is using
> > two GNUmed wxpython instances talking to the database through gmPG2 and
> > friends different from one GNUmed wxypython instance and one web
> > instance ?
>
> By "web instance" people are assuming that the "web" thing
> has its own ideas about the database management.
Yeah the field is very broad. There is no such thing as a common understanding
of what a web instance may involve. It may be anything between a few static
html pages on top of the GNUmed middleware to some combination of AJAX client
side stuff working the database through some server framework by completely
bypassing the GNUmed middleware.
I guess for an in praxis setting (50 clients max) I was looking for this
---------------------------------------------------------------------------------------
optional client side framework for dynamic content
(pyjamas or js framework)
|
webbrowser (displaying html)
|
webserver (e.g. cherrypy)
|
gmPG2
|
psycopg2
|
PG
I guess what I don't have in mind is
----------------------------------------------
optional client side framework
|
webbrowser
|
django orm
|
PG
----------------------------------------------------
It took a while to understand the whole web thing and I am still not totally
clear on some concepts. They evolve so fast and lack standardisation in some
areas (such as client side widgets across frameworks)
Sebastian