. Just got the 3.0 configs to a point where I
> liked 'em, too.
>
> Saludos,
> Jose.
>
> On Oct 29, 2008, at 5:16 PM, Jean-Francois Lamy wrote:
>
>> Same here. I don't quite get why the old style files can't be
>> parsed to
>> whatever newfa
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
Nope.
Setting this variable did NOT do the trick for us.
If someone can post a full "howto", it would be gratefully appreciated.
jfl
-Message d'origine-
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
fu
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-bi
I see several points in version 3.0.25 regarding isapi_srun.dll
Can anyone tell me if isapi_srun.dll now runs on 64 bit windows systems, and
if so, what the magic required is ?
I've had over half a dozen personal queries for this since posting a note
over a year ago, and yes, there is a bug open
Many of our clients run IIS in order to front .net apps or sharepoint. It
is therefore convenient to be able to add resin as a back-end through
isapi_srun.dll
Our understanding is that the provided dll is a 32 bit dll. We have never
been able to figure out the magic required to make it work on a
We use both C3P0 and DBCP exactly for that purpose; we read information from
a separate configuration file found on the classpath, build a connexion
pool, and register the pool by calling the JNDI API.
In our experience, C3P0 is a touch faster and more stable than DBCP, but the
error messages fr
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 p
I am trying to understand how resin, apache and proxies interact with
respect to caching.
I have a jsp page which is meant to be always dynamic; headers are used to
prevent it from being cached.
However, the page loads js, css, and various images, which I would like to
be cached.
Currently, the
My understanding is that SSL support is only available for Resin Pro, and
client wont 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.
Since I wasn’t able to get Apache going as a front-end
to resin, I decided to try IIS...
I’m unable to get the ISAPI filter to
load under the 64bit version of Windows 2003. I have performed all the steps
outlined in the installation (I have gotten this to work several timesbefore
und
Configuration: Windows Server 2003, 64 bit edition +
resin 3.0.21 + Apache 2.2.3
When trying to configure Apache 2.2 to talk to resin, I get
an error message stating that the specified module (mod_caucho.dll) could not be
found. I get the message no matter whether I use setup.exe
Hi!
A couple newbie questions regarding portlets.
Reading the documentation on caucho.com, the portlet API
referenced is JSR 162; most references to portlets seem to reference JSR 168. Is
Resin3 compliant with the latter? Does it matter?
My end goal is for a Vignette server
13 matches
Mail list logo