Categories | Tags | Advanced Search

2008 May (0) April (5) March (1) February (0) January (3)	2007 December (0) November (3) October (0) September (2) August (1) July (3) June (1) May (1) April (0) March (0) February (2) January (1)
2006 December (2) November (0) October (2) September (0) August (1) July (2) June (0) May (1) April (0) March (0) February (0) January (0)	2005 December (0) November (1) October (0) September (1) August (0) July (0) June (0) May (0) April (0) March (0) February (0) January (0)
2004 December (0) November (0) October (1) September (1) August (0) July (1) June (2) May (1) April (0) March (0) February (1) January (0)	2003 December (0) November (1)

• Patterns for Servlet 3.0 suspend usage.
  This blog presents 5 patterns of suspend usage for servlet-3.0, which can help explain the generic cases, provide a template for specific implementations and/or be the basis of frameworks to help developers.Read more...Tags : servlet opensource http ajax ...
• JSR-315 Needs YOU!
  The expert group for JSR 315 (servlet-3.0) has come to a bit of an impasse regarding some new features for auto discovery of servlets and filters. Some members of the EG have some security/flexibility concerns regarding these features, but others do not ...
• Use-Cases for Async Servlets
  Pre-release 0 of Jetty 7.0.0 is now available and includes a preview of the proposed Servlet 3.0 API for asynchronous servlets. This blog looks at 4 cool things you can do with asynchronous servlets and how they can be implemented using the proposed ...
• Jetty Improves in Netcraft survey (again)
  As with most open source projects, it's very hard to get a measure of who/how/where/why Jetty is being used a deployed. Downloads long ago became meaningless with the advent of many available bundling and distribution channels. The Netcraft Web Survey is ...
• Jesse Mcconnell at Webtide
  Jesse Mcconnell (of maven background) has joined Webtide. Jesse has been with us for several months now and we are really please to have his experience and skills being applied to the Jetty project and for Webtide clients. Jesse has started a blog, and ...
• Servlet 3.0 sampler patch
  A patch is now available for the development version of Jetty that introduces some of the proposed features for Servlet 3.0. Key among these is a suspend/resume API on the request object that is a proposed standardization the Jetty Continuation mechanism ...
• Client-side session replication for clusters
  Techniques for replicating session data include distributing: to all nodes in a cluster; to a subset of the nodes in the cluster; to a database; to a cluster server; etc. etc. To this range of solutions, cometd/bayeux now adds the possibility of using the ...
• 20,000 reasons why Jetty scales
  I have published a comet Daily article that describes how I have benchmarked Jetty's Cometd implementationof dojox Bayeux protocol to 20,000 simultaneous clients. This blog looks at the same results from a more Jetty centric view point.Read more...Tags : ...
• Blocking Servlets, Asynchronous Transport
  The web-2.0 Ajax Comet use-cases have been getting most the attention when it comes to asynchronous features of servlet containers. The Asynchronous features are needed so that a request may wait without a thread allocated while waiting for a comet event ...
• Asynchronous IO is hard!
  The tomcat 6 developers have proposed an asynchronous IO extension as their solution for Comet and Ajax push. I have long argued that asynchronous handling is needed for Servlets (for comet and other use-cases), but that it is very important to make the ...

• Re: Servlet Performance Report - The Jetty Response.
  Fixed! although this points to an old jetty-5 guide and we probably need to update it a bit. However the general advice is still good.
• Re: Servlet Performance Report - The Jetty Response.
  "Jetty Optimisation Guide" link seems broken
• Re: JSR-315 Needs YOU!
  I prefer the current configuration of filters instead of auto discovery. It's clean and elegant, and most importantly, manageable. Usually, a web app does not have many filters. I would like to spend time on configuring filters instead of figuring out ...
• Re: JSR-315 Needs YOU!
  If there will be no way of saying which jars should be used for autodiscovery then i will be forced to define everything in web.xml as in old days. We can't afford not knowing what is actually used. This new feature would be useless for us. So i ...
• Re: JSR-315 Needs YOU!
  The servlet spec needs to handle login and user attributes, not just delegate the problem to JAAS. The EG really needs to look long and hard at JSR 286 and figure out what they can do to make the next Portlet Spec better. Many of its deficiencies are a ...
• Re: JSR-315 Needs YOU!
  Never mind web.xml... please, please give me programmatic login and remember me!
• Re: JSR-315 Needs YOU!
  The proposed include mechanism can specify individual classes, web.xml fragments and/or TLD descriptors. So long as those are internally consistent, then ordering should be able to be done at a very fine level of granularity.
• Re: JSR-315 Needs YOU!
  Sarah, scanning can find annotations and web.xml fragments. However it cannot discover what filters and servlets a Listener may configure. Listeners may call arbitrary code on the classpath to determine what filters and servlets it will deploy via the ...
• Re: JSR-315 Needs YOU!
  FYI, There is also a thread on this on The Server Side: http://www.theserver...
• Re: JSR-315 Needs YOU!
  I don't see how the proposed solution can handle order dependency of annotated servlet-mapping or filter-mapping. For example, incorporating multiple filters in a chain, one might want to order them in a different order than auto-discovered, even when ...

Webtide blogs
Webtide News
Jan's blog
Greg's blog
Jesse's Blog
Adam's Blog
Jetty Case Studies