Re: [Resin-interest] 3.2 experience?

2008-10-29 Thread Jean-Francois Lamy
Same here.  I don't quite get why the old style files can't be parsed to
whatever newfangled data structure is used by the new version, with whatever
defaults best approximate the old behaviour.

Jean-François Lamy
Teximus

-Message d'origine-
De : [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] De la part de Rob Lockstone
Envoyé : 29 octobre 2008 19:43
À : General Discussion for the Resin application server
Objet : Re: [Resin-interest] 3.2 experience?

I'm with you, Leonid! The config file changes from one major release  
to the next has always been a big pain. I know that some are needed  
from time to time, but this has often been the biggest hurdle in  
upgrading for us. We're still on 3.0.x because I haven't yet had the  
time to vet and apply the significant config file changes between 3.0  
and 3.1. 3.2? Forget about it! (Not stable enough for us yet anyway.)

Rob

On Oct 29, 2008, at 10:44, Leonid Geller wrote:

 In general I like how 3.2 has fewer jars to go around. Hessian is  
 the exception. It would be nice if all of Hessian code was factored  
 out into a separate library in 3.2.x, so we can drop it into other  
 containers, whether they are applications running 3.1.x or perhaps  
 third party apps like tomcat.

 Also it appears 3.2 is not backward compatible from config stand- 
 point. It is not enough to simply rename .conf to .xml, some  
 configuration elements that used to be optional are required now.  
 This raises the barrier to upgrade from 3.1.x to 3.2.x

 -Leonid


 -Original Message-
 From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] 
 ] On Behalf Of Emil Ong
 Sent: Wednesday, October 29, 2008 12:36 PM
 To: General Discussion for the Resin application server
 Subject: [Resin-interest] 3.2 experience?

 Resin 3.2.1 is our latest release in the 3.2 branch, which is our
 development branch.  This branch still undergoes our extensive release
 testing, but has many changes which have not been quite as vetted  
 Resin
 3.1 in production use.

 If you are using 3.2.0 or 3.2.1, what have your experiences been?
 Are you using it in production?  After testing, did you decide to
 use Resin 3.2. or to stick with Resin 3.1?  Why?  What did your  
 testing
 include?  What features do you like and what would you like to see?

 I appreciate any feedback you have to offer as we've gotten a few
 questions from people interested in using Resin 3.2, but want to hear
 from other folks who've kicked the tires a bit.

 Thanks,
 Emil



___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest



___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest


Re: [Resin-interest] Win64 ISAPI (was: 3.0.25 Update)

2007-12-11 Thread Jean-Francois Lamy
I am quite sure that we tried the equivalent change through the user
interface, but we'll double check.

jfl

-Message d'origine-
De la part de Emil Ong
Envoyé : 11 décembre 2007 13:06

We have found that the 32-bit DLL works on 64-bit systems as well,
but we are planning to release a 64-bit compiled version in the
future.  Some of people have found it necessary to make a change
to the registry to make sure this DLL is compatible:  You might
need to set the key W3SVC/AppPools/Enable32bitAppOnWin64 to 1.

Please let me know if this does the trick for you and we can add it to
the documentation, at least until we can create a 64-bit native DLL.

Best,
Emil




___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest


Re: [Resin-interest] 304 status

2007-05-24 Thread Jean-Francois Lamy
Thanks Serge, the document proved to be just what we needed.  We fixed our
issues with a somewhat brain dead proxy as follows
a) making sure Apache was serving documents and images directly (and not
delegating to Resin)
b) Activating mod_expires and using the Expires directives to tell the
stupid proxy to keep images, css and so on in cache for a day
c) Removing a vary: user-agent header that was preventing compressed
content from being. We believe this to be a bug in the proxy. Luckily the
largish css and js files we wanted compressed do not vary by user agent.

Jean-François Lamy
Teximus


-Message d'origine-
De : [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] De la part de Serge Knystautas
Envoyé : 17 mai 2007 13:08
À : General Discussion for the Resin application server
Objet : Re: [Resin-interest] 304 status

Jean-François,

This is the best write-up I've seen on how browsers and proxy servers 
cache:

http://www.mnot.net/cache_docs/





___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest


[Resin-interest] SSL, mod_caucho for Apache 2.2

2007-04-05 Thread Jean-Francois Lamy
My understanding is that SSL support is only available for Resin Pro, and
client won’t shell out 1000$ for running on a dual-core PC.

 

So plan B is to install Apache.  Looking at my 3.0.21 download, I only see
mod_caucho for Apache 2.0.  So my understanding is that I need to run legacy
Apache 2.0.59 to get SSL support, or has Apache 2.2 support been added since
?

 

Is this correct ?

 

Jean-François Lamy

Technologies Teximus inc.

www.teximus.com

+1 514.878.1577 (Canada)

+33(0) 8.70.44.49.02 (Europe)

 

 

___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest