Re: [Resin-interest] Does Resin comet support work with non-blocking IO?

2008-05-06 Thread Tim Perrett 
Hey Scott

 As long as you're returning from the resume call, the comet support
 doesn't use a thread.  So there's no blocking I/O at all, and thread-
 max shouldn't apply.

So to clarify, after a call is suspended, it returns the thread to the  
thread pool?

Cheers

Tim


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

Re: [Resin-interest] Ant and JSPCompiler

2008-05-06 Thread rafael.munoz 

Thank you a lot. This work like a charm :)


Mattias Jiderhamn-4 wrote:
 
 Try
 
 target name=precompile-jsp description=precompile jsp
echo message=precompiling JSPs: app-dir=${home.war}/
java classname=com.caucho.jsp.JspCompiler fork=true 
   classpath refid=resin.classpath /
   arg line=-app-dir ${home.war} ${home.war} /
/java
 /target
 
 
 Note the extra ${home.war} in the arg line which means compile this dir 
 (and subdirs).
 
  /Mattias Jiderhamn
 
 
 ___
 resin-interest mailing list
 resin-interest@caucho.com
 http://maillist.caucho.com/mailman/listinfo/resin-interest
 
 

-- 
View this message in context: 
http://www.nabble.com/Ant-and-JSPCompiler-tp17061443p17082599.html
Sent from the Resin mailing list archive at Nabble.com.



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

Re: [Resin-interest] Does Resin comet support work with non-blocking IO?

2008-05-06 Thread Scott Ferguson 

On May 6, 2008, at 1:22 AM, Tim Perrett wrote:

 Hey Scott

 As long as you're returning from the resume call, the comet support
 doesn't use a thread.  So there's no blocking I/O at all, and thread-
 max shouldn't apply.

 So to clarify, after a call is suspended, it returns the thread to the
 thread pool?

That's correct.

Technically, the implementation isn't nonblocking-i/o because comet is  
server-push, i.e. a write-only technology, so there's no need for  
blocking i/o in the first place.

As a comparison, HMTP (http://caucho.com/resin/doc/hmtp.xtp), does use  
nonblocking i/o, because reads in HMTP are asyncronous.  Jabber (XMPP)  
is the same, and needs nonblocking i/o as well.

-- Scott



 Cheers

 Tim


 ___
 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 3.1.6

2008-05-06 Thread Scott Ferguson 
Resin 3.1.6 is now available.  The 3.1.x tree is now the stable  
version and will contain only bug fixes.  New development will go into  
the 3.2.x tree.

The release notes are at http://caucho.com/resin/changes/resin-3.1.6.xtp
The detailed changelog is at http://caucho.com/resin/changes/changes.xtp

1. Resin JSF

Resin's JSF implementation has been promoted to the 3.1.6 release.   
The JSF implementation includes a large number of bug fixes and  
compatibility testing.  Resin's JSF includes to important  
enhancements: direct JSP implementation and Hessian serialization,  
both of which improve performance and reduce session size.

2. Quercus (PHP)

A large number of bug fixes are included in the Quercus release.   
We've moved our focus to a killer app strategy, where the first  
priority of Quercus is keeping up to date with new killer app  
versions.  The killer apps are currently:

   Mediawiki 1.12 (wikipedia)
   Drupal 6.0
   phpBB3
   Typo3
   Wordpress 2.5.1

3. HMTP (Hessian Message Transport Protocol)

   http://caucho.com/resin/doc/hmtp.xtp

HMTP is all about putting the interactive in RIA (rich interactive  
applications.)  It's a high-performance, bidirectional, asynchronous  
messaging system based on Hessian and XMPP (Jabber IM).   The current  
implementations are in Java and Flash.

The underlying model is a Brokered Agent Messaging (bam), which is the  
XMPP model.  Essentially, it's a hub-and-spoke messaging model with  
dynamic services.  Agents are things like a chat login, or a chat room  
nickname, or a game's player.

We think HMTP is the next step in web interactivity, leapfrogging over  
the interim Ajax/Comet techniques.


4. scheduled-task

   http://caucho.com/resin/doc/resources.xtp

scheduled-task is a nice convenience bean for scheduling cron jobs.   
The full cron syntax is supported.  scheduled-task can start Runnable  
beans automatically, or invoke an EL method expression, or execute a  
URL (convenient for PHP cron scripts.)

5. administration/reliability

   http://caucho.com/resin/doc/resin-admin.xtp

For Resin-Pro, the administration task now checks CPU usage every 60  
seconds, either logging the results, or logging a thread dump if the  
cpu is excessive.  It's possible to configure the admin to restart  
Resin if the CPU usage it too high as wel.

6. logging

   http://caucho.com/resin/doc/config-log.xtp

We've cleaned up the logging a bit, making it easier to configure  
custom logging Handlers and Formatting tools.  In addition, we've  
split out log-handler as a separate configuration item, which  
configures the log handlers directly.  logger configures the  
Loggers.  (The older log is now discouraged since it combines both  
and is a bit confusing.)

The logging has some new handlers: event:, jms:, and hmtp: which  
lets you publish logging messages to WebBeans events, JMS, and HMTP  
respectively.

share and enjoy!

-- Scott




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