From george at ringdevelopment.com  Thu Nov  9 11:10:32 2006
From: george at ringdevelopment.com (George Pauly)
Date: Wed, 08 Nov 2006 19:10:32 -0500
Subject: [albatross-users] Is Albatross right for my app?
Message-ID: <1163031033.7476.149.camel@localhost.localdomain>

I'm working on a stateful ajax/comet app.  This involves maintaining
state for the client browser app over a long period with many
interprocess communications to a server daemon.  Ideally, this would be
runnable on a shared hosting ISP running *nix/Apache.  This might
involve a cgi intermediate that plugs into the daemon.

Albatross' server daemon sounds like it might help, but I don't think I
need all the template/page/macro parts.

Any advice appreciated.

If the advice is to develop a custom daemon app, why did Albatross go
with sockets instead of named pipes for interprocess communication? 

Thanks,

George


-- 
George Pauly
Ring Development
www.ringdevelopment.com



From andrewm at object-craft.com.au  Thu Nov  9 12:30:25 2006
From: andrewm at object-craft.com.au (Andrew McNamara)
Date: Thu, 09 Nov 2006 12:30:25 +1100
Subject: [albatross-users] Is Albatross right for my app? 
In-Reply-To: <1163031033.7476.149.camel@localhost.localdomain> 
References: <1163031033.7476.149.camel@localhost.localdomain>
Message-ID: <20061109013025.E7572D423E@longblack.object-craft.com.au>

>I'm working on a stateful ajax/comet app.  This involves maintaining
>state for the client browser app over a long period with many
>interprocess communications to a server daemon.  Ideally, this would be
>runnable on a shared hosting ISP running *nix/Apache.  This might
>involve a cgi intermediate that plugs into the daemon.
>
>Albatross' server daemon sounds like it might help, but I don't think I
>need all the template/page/macro parts.

I think Albatross is somewhat tangential to what you want. While people
have written AJAX apps that work in conjunction with an Albatross
application, they're typically hybrids (part CGI, part AJAX), whereas
it sounds like yours is purely AJAX.

>If the advice is to develop a custom daemon app, why did Albatross go
>with sockets instead of named pipes for interprocess communication? 

Using sockets for the session daemon allows us to do things like have
multiple load-balanced web servers using one session server, so no
matter which web server the client hits, that web server has access to
the current session. If the communication between the application and
the session daemon was via a named pipe, both would have to reside on
the same machine.

-- 
Andrew McNamara, Senior Developer, Object Craft
http://www.object-craft.com.au/


From stanpinte at sauvages.be  Sat Nov 25 03:19:39 2006
From: stanpinte at sauvages.be (Stan Pinte)
Date: Fri, 24 Nov 2006 17:19:39 +0100
Subject: [albatross-users] validate_request in Albatross docstring
Message-ID: <45671B9B.4040002@sauvages.be>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

Thanks for that very good example
http://www.object-craft.com.au/projects/albatross/wiki/Handling_Authentication.

However, I just lost some precious minutes because of the wrong
docstring for method

validate_request in Albatross latest online doc
(http://object-craft.com.au/projects/albatross/albatross/pack-app.html#l2h-272)

Could it be updated, so that it explains what it means to return 0,
and what it means to return 1?

Kind regards,

Stan.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFZxub/PmuubxPWAIRAuAAAJ95CSKe/mp/E5Bq1X6B8dEgbaOGowCeLImK
oIAMsExObSsDfMce+11RV0M=
=9sYW
-----END PGP SIGNATURE-----