X-Original-To: alpine-devel@lists.alpinelinux.org
Delivered-To: alpine-devel@mail.alpinelinux.org
Received: from mail-pa0-f54.google.com (mail-pa0-f54.google.com [209.85.220.54])
	(using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
	(No client certificate requested)
	by mail.alpinelinux.org (Postfix) with ESMTPS id 390D9DC0153;
	Sat,  8 Dec 2012 18:12:28 +0000 (UTC)
Received: by mail-pa0-f54.google.com with SMTP id bi5so1179810pad.13
        for <multiple recipients>; Sat, 08 Dec 2012 10:12:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=from:reply-to:to:subject:date:user-agent:references:in-reply-to:cc
         :mime-version:content-type:content-transfer-encoding:message-id;
        bh=b3OB2R0cG6CZOluBTaWcZTqfQmV+24u/gIGUpvdCplA=;
        b=fACA5+keL7VKUiG/C/wUoDCKoLMB3tN5+kud++5Fl6Wat6ysW5HqRGEjQysJdkF4zh
         bDX3MJ5nthJEHVZn6aUi9Ne+myyrvaJ3h5+JoPHjKCHGzveshjpgYUZsNuCD6M24bnbe
         aZ/bIx81vfY+i9peT7YMZ8zJi4ystFX1eSE4nZZelVqmYR+FwxewTZPz+nJYjf4tStaT
         vo1utVDVkm96nuPMrk/o1tgDSnRahM3NqF6aRjhF+0hLvWl0wfcpcrKkJAvPF9cVYmg/
         rh6Fq5wkUsotO+7a4tHvKF6BzKVVm+4ULJoTo3WGUFZZsbZJh3Tgwy3cZwJEvnbXTrbf
         2cgg==
Received: by 10.68.143.129 with SMTP id se1mr25522759pbb.67.1354990347926;
        Sat, 08 Dec 2012 10:12:27 -0800 (PST)
Received: from microknoppix.localnet ([117.226.154.3])
        by mx.google.com with ESMTPS id o11sm8779637pby.8.2012.12.08.10.12.23
        (version=TLSv1/SSLv3 cipher=OTHER);
        Sat, 08 Dec 2012 10:12:27 -0800 (PST)
From: "V.Krishn" <vkrishn4@gmail.com>
Reply-To: vkrishn4@gmail.com
To: Kaarle Ritvanen <kaarle.ritvanen@datakunkku.fi>
Subject: Re: [acf] Re: [alpine-devel] Ideas for a new config framework, ACF2
Date: Sat, 8 Dec 2012 23:37:52 +0530
User-Agent: KMail/1.13.7 (Linux/3.3.7-64; KDE/4.7.4; x86_64; ; )
References: <20121129152317.69585a4f@ncopa-desktop.alpinelinux.org> <0467883F-A7E4-4156-940E-9F5F10AD5FB2@gmx.net> <alpine.LFD.2.02.1212081711140.8590@kunkku.net>
In-Reply-To: <alpine.LFD.2.02.1212081711140.8590@kunkku.net>
Cc: "alpine-devel@lists.alpinelinux.org" <alpine-devel@lists.alpinelinux.org>,
 "acf@lists.alpinelinux.org" <acf@lists.alpinelinux.org>
X-Mailinglist: alpine-devel
Precedence: list
List-Id: Alpine Development <alpine-devel.lists.alpinelinux.org>
List-Unsubscribe: 
	<mailto:alpine-devel+unsubscribe@lists.alpinelinux.org?subject=unsubscribe>
List-Post: <mailto:alpine-devel@lists.alpinelinux.org>
List-Help: <mailto:alpine-devel+help@lists.alpinelinux.org?subject=help>
List-Subscribe: 
	<mailto:alpine-devel+subscribe@lists.alpinelinux.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="iso-8859-15"
Content-Transfer-Encoding: 7bit
Message-Id: <201212082337.52917.vkrishn4@gmail.com>

On Saturday, December 08, 2012 10:32:52 PM you wrote:

> Some ACF use cases require streaming status information back to the client
> as the operation progresses. 

Thinking of "streaming status information" would it good idea to de-couple 
ACF's streaming part info into AMF (Alpine Monitoring Framework) ?

> Django does not support this very well, at
> least in any production release. (Version 1.5 will have
> StreamingHttpResponse class.)
> 
> Finally, remember that Django is a framework intended for implementing
> relational database-oriented web applications with server-side HTML
> templating. While it would be possible to implement CLI and SNMP
> interfaces for Django models, the framework does not really help in that
> effort. We also want to include dynamic state information e.g. from /proc,

Does this mean kinda  web pub/sub system?

> but Django does not help there at all. I think it is better to design the
> framework to take these use cases into account at model API level. As I
> said, Django is a nice framework for the purposes it was designed to and
> obviously has been developed by smart programmers. We will indeed let its
> design influence ours. Even if we decide to implement the web interface as
> a single page application (in JavaScript), we can apply some principles
> found e.g. in Django's form API. We should also take a look at Dojo
> Toolkit.

On whole I think having a light weight system not tied to one scripting 
language should be good choice.

Choice of persistence manager should be such that any binding with other web 
framework/scripting language be possible.
Eg.  ACF - lua
       AMF - php

Just a thought.

-- 
Regards.
V.Krishn


---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---