From bmoelk at brainendeavor.com  Tue Dec  9 23:54:26 2008
From: bmoelk at brainendeavor.com (Brian Moelk)
Date: Wed, 10 Dec 2008 04:54:26 +0000
Subject: [Swiftiply-users] cache-control header and nanite
Message-ID: <493f4b82105d1_3f63fe79854c47c2278a@app01.zenbe.com.tmail>

I have two questions:

1) is there any way to control the cache-control header returned from swiftiply for static files?  If not, are there plans for adding this?  I understand that swiftiply isn't a full blown webserver, but I believe this would improve overall performance and is easy enough to add if it's already serving out static files.

2) I've heard a little bit about Nanite.  Nanite seems to be more service oriented (not necessarily web based) and leverages RabbitMQ/Erlang, etc.  while Swiftiply is a reverse proxy focused on web applications.  Both seem to allow dynamic expansion of backend "workers".  Is that a fair compare/contrast between Nanite and Swiftiply?  Are you involved in Nanite at all?

Thanks,
-Brian Moelk

From wyhaines at gmail.com  Thu Dec 11 17:45:10 2008
From: wyhaines at gmail.com (Kirk Haines)
Date: Thu, 11 Dec 2008 15:45:10 -0700
Subject: [Swiftiply-users] cache-control header and nanite
In-Reply-To: <493f4b82105d1_3f63fe79854c47c2278a@app01.zenbe.com.tmail>
References: <493f4b82105d1_3f63fe79854c47c2278a@app01.zenbe.com.tmail>
Message-ID: <f4cd26df0812111445j52ddc95fmaf625ade1e79e3a0@mail.gmail.com>

On Tue, Dec 9, 2008 at 9:54 PM, Brian Moelk <bmoelk at brainendeavor.com> wrote:
> I have two questions:
>
> 1) is there any way to control the cache-control header returned from swiftiply for static files?  If not, are there plans for adding this?  I understand that swiftiply isn't a full blown webserver, but I believe this would improve overall performance and is easy enough to add if it's already serving out static files.

Yeah.  I've thought about this, and right now I plan to add it as a
simple config option which all one to provide any arbitrary headers
that one wants attached to static file responses.

> 2) I've heard a little bit about Nanite.  Nanite seems to be more service oriented (not necessarily web based) and leverages RabbitMQ/Erlang, etc.  while Swiftiply is a reverse proxy focused on web applications.  Both seem to allow dynamic expansion of backend "workers".  Is that a fair compare/contrast between Nanite and Swiftiply?  Are you involved in Nanite at all?

I'm not involved with Nanite directly, but I have thought about
allowing requests to be submitted to a Nanite queue, for handling by
nanite workers.  There would be more latency than there is with
Swiftiply workers, but it could be really nice for requests that
aren't really fast anyway.


Kirk Haines