Re: [Resin-interest] Change Port via web.xml
Hi, I'm not sure how the hoster came to told you that, but the web.xml file is the configuration for a specific application/context inside a host, and there can be several applications configured for a host, so it asolutely makes no sense configuring the host's port at the application level. In order to configure the port, you have to have access to the resin.conf file, as that's where the host data is defined. On the other hand, the usual setup is having an Apache up-front (which has the 80 port configured) and that redirects to the appropriate resin instance. If that was the case, if the URLS do not work, one would think the Apache is not redirecting the requests correctly. an 500-err is certainly not enough information to know what is going on. In any case, back to the beginning, changing the server port is not someting one does from the application. It might have been a misunderstanding because it makes no sense. S! D. doneme escribió: Hello there! Some weeks ago I rented webspace on a hosted server with JSP-Support - a Resin is running. After enabling JSP-functionality, my websites (html and jsp) were not able to be accessed anymore without appending the port 8080 (e.g. http://myurl.com:8080/index.html, http://myurl.com:8080/test.jsp). Without the port, the only answer was an 500-err. I don't like the fact, that I have to add the port everytime I (or someone else) wants to enter my website. After some correspondence the hoster told me, that I have to edit the web.xml, in which I can map the port 80 to every access. But how? I never found an example of someone doing this, but configuring Resin conf-file (on which I have no access - just my hoster). Any ideas? Greetings, Eric ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] Resin 3.0 and 3.1 with one Apache?
On Mar 10, 2009, at 6:44 AM, Hari Selvarajan wrote: Greetings, We run several web applications on Resin 3.0 with Apache and mod_caucho as a front-end. For a new web application that we're developing, which will run under the same site, we'd like to use Resin 3.1 in a different JVM. Something like this: We're using the mod_caucho from Resin 3.1 for requests to both Resin instances. This works well in basic tests but I'm wondering if there's anything we need to be aware of while using mod_caucho from Resin 3.1 with Resin 3.0. I would hate to find out that we were doing something risky when we got to our load tests so it seemed wise to ask the community in advance. I wouldn't recommend this, because we do change the communication between the two from time to time (generally relating to the pooling configuration items.) You might consider using something like mod_proxy for one of the versions. Because mod_proxy just uses HTTP as the communication protocol, which any version of Resin understands, you'd avoid any conflict. -- Scott Thanks, - Hari ___ 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
[Resin-interest] Why Apache?
After watching a few of these threads about people using mod_caucho with Apache, it dawned on me to ask an open-ended question: Why use Apache at all? I am sure there are good reasons for it out there, so I am just curious what the use-case is for using Apache plus Resin instead of using just Resin? ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] Why Apache?
Apparently they prefer the log output. I'll try to get you more specifics if I can. Scott Ferguson wrote: On Mar 10, 2009, at 10:19 AM, Daniel J. Doughty wrote: Some of my developers prefer how Apache logs activity. Can you give some more details? The Apache /server-status or the log output or something else? Some of that logging might be straightforward to add to Resin. -- Scott Aaron Freeman wrote: After watching a few of these threads about people using mod_caucho with Apache, it dawned on me to ask an open-ended question: Why use Apache at all? I am sure there are good reasons for it out there, so I am just curious what the use-case is for using Apache plus Resin instead of using just Resin? ___ 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 ___ 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] Why Apache?
Hi, Why use Apache at all? there's more than one reason. Serving different sites/services on the same server, not all can be served by resin for various reasons: a) Rewriting Service: mod_rewrite has no real pendent b) Different Servlet-Containers on port 80: There are a couple of services which just wont run under resin (my favorite is TeamCity which runs on a Tomcat instance because of that). c) PHP Not everything's running with resin and there are some projects out there which just need the Apache-PHP plugin d) Different resin-instances on port 80: I don't want my TestEnvironment interfere with Live Services when a restart of the container is necessary. Apache is a nice and powerful software to combine these different aspects all. Best regards, --- Jan. ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] Why Apache?
Static file serving, perhaps? I don't know the current benchmarks but Apache has always had the reputation of being very fast for static files, whereas that's not what resin is optimized for. I say this from the POV of not using Apache at all, though: we use resin behind HAProxy for load balancing, and a lighttpd instance for image files. Rachel On Tue, Mar 10, 2009 at 10:14 AM, Aaron Freeman aaron.free...@layerz.com wrote: After watching a few of these threads about people using mod_caucho with Apache, it dawned on me to ask an open-ended question: Why use Apache at all? I am sure there are good reasons for it out there, so I am just curious what the use-case is for using Apache plus Resin instead of using just Resin? ___ 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] Why Apache?
I like very mych Resin as app. server. but if we talk about http servers I think apache is more reliable, more documented, more flexible and faster. e.g. LocationMatch \.gif$ Header set Cache-Control post-check=36000,pre-check=99 /LocationMatch Scott Ferguson wrote: On Mar 10, 2009, at 10:19 AM, Daniel J. Doughty wrote: Some of my developers prefer how Apache logs activity. Can you give some more details? The Apache /server-status or the log output or something else? Some of that logging might be straightforward to add to Resin. -- Scott Aaron Freeman wrote: After watching a few of these threads about people using mod_caucho with Apache, it dawned on me to ask an open-ended question: Why use Apache at all? I am sure there are good reasons for it out there, so I am just curious what the use-case is for using Apache plus Resin instead of using just Resin? ___ 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 ___ 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] Why Apache?
I don't agree with part 1 even, with the advent of vmware/xen/virtualbox there is no reason to cram a bunch of stuff on a single server. It makes your infrastructure way less upgradable, reliable, and testable. a) The rewriting in resin is pretty good, its all regex, just like any other rewrite. You may have to learn some new stuff, but that kind of how IT works :) b) You can do this with resin vhosts as well, either ip based or ipless. c) You can also do this with resin :) http://quercus.caucho.com/ d) Same thing, but if you use a virtualization product its a no brainer to clone production instances for QA on the same hardware. I find resin by itself to be faster and easier to manage. The less software you run the easier and safer your site will be. Running apache introduces more code that you need to patch and manage, and apache is not the safest or fastest webserver on the market. Just some food for thought :) On Tue, Mar 10, 2009 at 1:41 PM, Jan Kriesten kries...@mail.footprint.dewrote: Hi, Why use Apache at all? there's more than one reason. Serving different sites/services on the same server, not all can be served by resin for various reasons: a) Rewriting Service: mod_rewrite has no real pendent b) Different Servlet-Containers on port 80: There are a couple of services which just wont run under resin (my favorite is TeamCity which runs on a Tomcat instance because of that). c) PHP Not everything's running with resin and there are some projects out there which just need the Apache-PHP plugin d) Different resin-instances on port 80: I don't want my TestEnvironment interfere with Live Services when a restart of the container is necessary. Apache is a nice and powerful software to combine these different aspects all. Best regards, --- Jan. ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest -- -jk ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] Why Apache?
On Mar 10, 2009, at 10:44 AM, Rachel McConnell wrote: Static file serving, perhaps? I don't know the current benchmarks but Apache has always had the reputation of being very fast for static files, whereas that's not what resin is optimized for. I say this from the POV of not using Apache at all, though: we use resin behind HAProxy for load balancing, and a lighttpd instance for image files. Actually, Resin's static file performance matches Apache's, because Apache really isn't all that fast. If you really need ultra fast static files, then something like lighttpd or nginx would be a better choice than Apache. -- Scott Rachel On Tue, Mar 10, 2009 at 10:14 AM, Aaron Freeman aaron.free...@layerz.com wrote: After watching a few of these threads about people using mod_caucho with Apache, it dawned on me to ask an open-ended question: Why use Apache at all? I am sure there are good reasons for it out there, so I am just curious what the use-case is for using Apache plus Resin instead of using just Resin? ___ 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 ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] Why Apache?
On Tue, Mar 10, 2009 at 12:14:36PM -0500, Aaron Freeman wrote: After watching a few of these threads about people using mod_caucho with Apache, it dawned on me to ask an open-ended question: Why use Apache at all? I am sure there are good reasons for it out there, so I am just curious what the use-case is for using Apache plus Resin instead of using just Resin? Thanks for asking this Aaron! We're getting a lot of useful feedback. (You tell that you've hit a nerve when so many people respond so quickly... :-)) From the point of view of support, I can say that whenever Apache enters the equation, the complexity goes way up. If there's any way you can avoid using Apache with Resin, I would recommend it. For those who need things like mod_perl or run other application servers, you may have no other choice. Someone else mentioned Apache mod_rewrite, which we have an alternative for in our rewrite dispatch rules: http://caucho.com/resin/doc/rewrite-tags.xtp I find the XML syntax much more readable than the line-noise syntax of mod_rewrite. Emil Emil Ong Chief Evangelist Caucho Technology, Inc. Tel. (858) 456-0300 mailto:e...@caucho.com http://blog.caucho.com/ Caucho: Reliable Open Source -- Resin: application server -- Quercus: PHP in Java -- Java CanDI: contexts and dependency injection ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] Why Apache?
I actually love IIS for static content, its very fast and the caching is great. It can beat apache hands down, but not sure on light ot ng. On Tue, Mar 10, 2009 at 1:52 PM, Scott Ferguson f...@caucho.com wrote: On Mar 10, 2009, at 10:44 AM, Rachel McConnell wrote: Static file serving, perhaps? I don't know the current benchmarks but Apache has always had the reputation of being very fast for static files, whereas that's not what resin is optimized for. I say this from the POV of not using Apache at all, though: we use resin behind HAProxy for load balancing, and a lighttpd instance for image files. Actually, Resin's static file performance matches Apache's, because Apache really isn't all that fast. If you really need ultra fast static files, then something like lighttpd or nginx would be a better choice than Apache. -- Scott Rachel On Tue, Mar 10, 2009 at 10:14 AM, Aaron Freeman aaron.free...@layerz.com wrote: After watching a few of these threads about people using mod_caucho with Apache, it dawned on me to ask an open-ended question: Why use Apache at all? I am sure there are good reasons for it out there, so I am just curious what the use-case is for using Apache plus Resin instead of using just Resin? ___ 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 ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest -- -jk ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] Why Apache?
Hi Scott, Here is my long wait question : How to configure Resin run with nginx? regards Wesley - Original Message - From: Scott Ferguson f...@caucho.com To: General Discussion for the Resin application server resin-interest@caucho.com Sent: Wednesday, March 11, 2009 1:52 AM Subject: Re: [Resin-interest] Why Apache? On Mar 10, 2009, at 10:44 AM, Rachel McConnell wrote: Static file serving, perhaps? I don't know the current benchmarks but Apache has always had the reputation of being very fast for static files, whereas that's not what resin is optimized for. I say this from the POV of not using Apache at all, though: we use resin behind HAProxy for load balancing, and a lighttpd instance for image files. Actually, Resin's static file performance matches Apache's, because Apache really isn't all that fast. If you really need ultra fast static files, then something like lighttpd or nginx would be a better choice than Apache. -- Scott Rachel On Tue, Mar 10, 2009 at 10:14 AM, Aaron Freeman aaron.free...@layerz.com wrote: After watching a few of these threads about people using mod_caucho with Apache, it dawned on me to ask an open-ended question: Why use Apache at all? I am sure there are good reasons for it out there, so I am just curious what the use-case is for using Apache plus Resin instead of using just Resin? ___ 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 ___ 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] Why Apache?
On Mar 10, 2009, at 7:14 AM, Aaron Freeman wrote: Why use Apache at all? you may have a situation where you haven't got a single webapp, but many webapps and other creatures living under a single host. in that case apache makes a nice top-level dispatcher, proxying requests to the various PHP, CGI, j2ee webapps, static content, and other assorted junk. -- joe ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] Why Apache?
Hi, a) The rewriting in resin is pretty good, its all regex, just like any other rewrite. You may have to learn some new stuff, but that kind of how IT works :) the rewriting in resin has it's limits - at least the last time I tried (I actually wrote to this list to get a replacement in 2007 - and was directed back to mod_rewrite!). mod_rewrite is pretty powerful. b) You can do this with resin vhosts as well, either ip based or ipless. You may have overlooked that I was talking about resin _not_ able to server as a servlet container for TeamCity, so I have to hook in TomCat. c) You can also do this with resin :) http://quercus.caucho.com/ No, you can't. And I don't want to bother about complaints of the 'normal' php-hacker serving low-traffic sites... d) Same thing, but if you use a virtualization product its a no brainer to clone production instances for QA on the same hardware. I don't argue virtualization can be your friend. But handling all more servers doesn't always make your life easier! As long as one server happily fullfills the needs I wont go that road. --- Jan ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] Why Apache?
I would dearly love to ditch Apache! The answer for us is our dedicated hoster uses Plesk, so as there are other users/apps on it who use the Plesk PHP panel for their regular admin we have to keep that. After watching a few of these threads about people using mod_caucho with Apache, it dawned on me to ask an open-ended question: Why use Apache at all? I am sure there are good reasons for it out there, so I am just curious what the use-case is for using Apache plus Resin instead of using just Resin? ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest No virus found in this incoming message. Checked by AVG - www.avg.com Version: 8.0.237 / Virus Database: 270.11.9/1992 - Release Date: 03/09/09 19:20:00 ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
[Resin-interest] Problem with rollover logs
Hi!
I just migrated from Resin 3.0.15 pro to 3.1.8 pro and have a problem
with log rollovers on Windows. I have defined the logs like this into
web-app-default:
stderr-log path=${resin.home}/../log/app.log rollover-size=1kb/
stdout-log path=${resin.home}/../log/app.log rollover-size=1kb/
Actually I use rollover-period with a longer time in production, the
above config just makes it faster to get to the error.
I'm running Resin as a Windows service with local system account. Now,
when the rollover happens, I see that the old log file gets renamed
and a new log file created, but the new file gets created as read-only
and writing to it fails with the following stack trace:
[2009-03-10 22:44:59] Can't create log directory /C:/Progs/app/log/app.log
java.io.IOException: 'C:\Progs\app\log\app.log' permission denied
at com.caucho.vfs.JniFilePathImpl.nativeOpenWrite(Native Method)
at
com.caucho.vfs.JniFilePathImpl.openAppendImpl(JniFilePathImpl.java:422)
at com.caucho.vfs.Path.openAppend(Path.java:1119)
at
com.caucho.log.AbstractRolloverLog.openLog(AbstractRolloverLog.java:504)
...
Does anyone have any idea why Resin creates the new log file as read-only?
Cheers,
Kai
___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] Problem with rollover logs
On Mar 10, 2009, at 1:58 PM, Kai Virkki wrote:
Hi!
I just migrated from Resin 3.0.15 pro to 3.1.8 pro and have a problem
with log rollovers on Windows. I have defined the logs like this into
web-app-default:
stderr-log path=${resin.home}/../log/app.log rollover-size=1kb/
stdout-log path=${resin.home}/../log/app.log rollover-size=1kb/
Actually I use rollover-period with a longer time in production, the
above config just makes it faster to get to the error.
I'm running Resin as a Windows service with local system account. Now,
when the rollover happens, I see that the old log file gets renamed
and a new log file created, but the new file gets created as read-only
and writing to it fails with the following stack trace:
[2009-03-10 22:44:59] Can't create log directory /C:/Progs/app/log/
app.log
java.io.IOException: 'C:\Progs\app\log\app.log' permission denied
at com.caucho.vfs.JniFilePathImpl.nativeOpenWrite(Native Method)
at
com.caucho.vfs.JniFilePathImpl.openAppendImpl(JniFilePathImpl.java:
422)
at com.caucho.vfs.Path.openAppend(Path.java:1119)
at
com.caucho.log.AbstractRolloverLog.openLog(AbstractRolloverLog.java:
504)
...
Does anyone have any idea why Resin creates the new log file as read-
only?
It shouldn't. They should be opened as read/write. I've added this
as http://bugs.caucho.com/view.php?id=3382
-- Scott
Cheers,
Kai
___
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
[Resin-interest] Resin Maven Plugin 3.2.1
Hi, I just upgraded the resin-maven-plugin from 3.1.5 to 3.2.1. The first time I entered mvn resin:run, it began downloading a ton of libraries and eventually failed, When I try to launch Resin via a mvn resin:run, Maven fails with a number of missing dependencies. It seems that the Caucho M2 Repository is missing a number of these dependencies: resin-ejb:jar:3.2.1 resin-j2ee-management:jar:3.2.1 resin-jca:jar:3.2.1 resin-jms:jar:3.2.1 resin-jsdk:jar:3.2.1 etc... Why are these dependencies not found in the Caucho M2 Repo? ( http://caucho.com/m2) This is from my pom.xml: plugin groupIdcom.caucho/groupId artifactIdresin-maven-plugin/artifactId version3.2.1/version /plugin Regards, Rob ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] Problem with rollover logs
Can this bug be upgraded to Super Major Urgent? Ok, seriously, after
hounding my management for weeks to finalize our Caucho contract, it's
finally in Accounting to do the Purchase Order and release the
funds. Then I'm on a tight schedule to start the upgrade process.
I was planning on using 3.1.8. But if this bug is real, it makes 3.1.8
essentially useless for us because we rely on our log files and I
can't upgrade to 3.1.8 and then upgrade *again* in a few weeks or
months after this has been fixed.
Rob
On Mar 10, 2009, at 14:08, Scott Ferguson wrote:
On Mar 10, 2009, at 1:58 PM, Kai Virkki wrote:
Hi!
I just migrated from Resin 3.0.15 pro to 3.1.8 pro and have a problem
with log rollovers on Windows. I have defined the logs like this into
web-app-default:
stderr-log path=${resin.home}/../log/app.log rollover-size=1kb/
stdout-log path=${resin.home}/../log/app.log rollover-size=1kb/
Actually I use rollover-period with a longer time in production, the
above config just makes it faster to get to the error.
I'm running Resin as a Windows service with local system account.
Now,
when the rollover happens, I see that the old log file gets renamed
and a new log file created, but the new file gets created as read-
only
and writing to it fails with the following stack trace:
[2009-03-10 22:44:59] Can't create log directory /C:/Progs/app/log/
app.log
java.io.IOException: 'C:\Progs\app\log\app.log' permission denied
at com.caucho.vfs.JniFilePathImpl.nativeOpenWrite(Native Method)
at
com.caucho.vfs.JniFilePathImpl.openAppendImpl(JniFilePathImpl.java:
422)
at com.caucho.vfs.Path.openAppend(Path.java:1119)
at
com.caucho.log.AbstractRolloverLog.openLog(AbstractRolloverLog.java:
504)
...
Does anyone have any idea why Resin creates the new log file as read-
only?
It shouldn't. They should be opened as read/write. I've added this
as http://bugs.caucho.com/view.php?id=3382
-- Scott
Cheers,
Kai
___
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
___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest
[Resin-interest] Session-timeout in web.xml has no effect
Hi all,
we're running resin 3.17a and seem to have a problem with session timeouts.
If I have in web.xml defined:
web-app xmlns=http://caucho.com/ns/resin;
session-config session-max=1
!-- 100 minute timeout --
session-timeout120/session-timeout
/session-config
It does not seem to have any effect on sessions.
I added session listener and outputted debugging information:
@Override
public void sessionCreated(final HttpSessionEvent arg0) {
log.info(New session started + arg0.getSession().getId()
+ creationtime + arg0.getSession().getCreationTime()
+ now is + new Date() + max interval
+ arg0.getSession().getMaxInactiveInterval());
}
@Override
public void sessionDestroyed(final HttpSessionEvent arg0) {
log
.info(Session destroyed
+ arg0.getSession().getId()
+ lifespan
+ (System.currentTimeMillis() - arg0.getSession()
.getCreationTime()) + now is + new Date()
+ last accessed
+ arg0.getSession().getLastAccessedTime()
+ max interval
+ arg0.getSession().getMaxInactiveInterval());
}
It seemed that max inactive interval on sessions was 10 minutes, no
matter what I set for session timeout in web.xml.
To get longer sessions, I then had to add in sessionlistener:
arg0.getSession().setMaxInactiveInterval(7200);
Any thoughts on where the problem might we lurking?
-huima
___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest
