Re: [webkit-dev] Safari Correctly Setting No-Cache via HTML

2007-11-02 Thread David D. Kilzer
[Please reply off-list as this is off topic.  I thought I'd post to the list in
case anyone wanders across this thread via Google search looking for an

Richard Glaser [EMAIL PROTECTED] wrote:

 Ok, this is really off-topic, but maybe someone has info on setting  
 JBoss 3.0 to add attributes to the HTTP header for no-cache with Safari.
 Here is feedback for a developer for our ARC system using Horizon,  
 which we are using Safari, but works fine with FireFox  IE.

Using an Apache web server as a reverse proxy in front of your JBoss 3.0
application server is certainly one possibility, but it can be a bit tricky to
configure.  (Note that if you have multi-level firewalls that create a DMZ,
it's best to place the Apache web server/reverse proxy in the DMZ, and the
JBoss application server behind the second firewall.)

Your other alternative is to write an HTTP Filter and add it to the web.xml
config file for JBoss.  This requires that JBoss 3.0 (or whatever Java
application server you're using) implement the Java Servlet 2.3 (or newer)
specification [1].


According to the documentation I found online [2], JBoss 3.0 implements both
Servlet 2.2 and Servlet 2.3 specifications.  I'm not sure how to switch between
them, but you'll want to enable the Servlet 2.3 mode.  (It may be as simple as
using a different web.xml config file that contains a Servlet 2.3 DTD at the
top and conforms to the 2.3 format.  Don't just change the DTD at the top of
the file and expect it to work, though!)

[2]  (search for 3.0 on the page)

The javax.servlet.Filter class has a fairly simple API [3].  Within the
doFilter() method, you (safely) cast the ServletResponse object to an
HttpServletResponse object, the call the addHeader() or setHeader() method [4]
on the response object to add your (anti-)caching headers.


Here are some good articles [5,6,7] that should give you more
background on filters.  In fact, article [7] is pretty much exactly what you
want to do since it allows you to add HTTP headers to outgoing responses.


Note that if you have a Java application server that implements Java Servlet
2.2 or older, your only option is to create a wrapper class for
javax.servlet.http.HttpServlet [8] that basically does the same thing as the
filter would do (adds/sets HTTP headers) for outgoing responses.  This is a
little more involved, but works just as well (assuming you don't have too many
filters that you wanted to use).  In terms of software patterns, this is the
Adapter Pattern [9,10].  Your new servlet would also be specified in the
web.xml config file for the application server.


Again, please reply off-list if you have additional questions.


webkit-dev mailing list

[webkit-dev] Re: WebKit/Gtk+ and how to contribute

2007-11-02 Thread Alp Toker

Holger Freyther wrote:

Hi all,

I'm glad the interest in WebKit/Gtk+ is so tremendous. While the current 
state of the port is quite good there are still a lot of things missing 
making it really kick ass. This includes Netscape Plugins, keyboard 
navigation, zooming, styling, finishing an API, networking improvements, 

So don't ask what WebKit/Gtk+ can do for you, but ask yourself what you 
can do for WebKit/Gtk+. And luckily the answer is very simple! File bugs 
and fix them!

1.) Filing bugs:
Go to and file bugs. Make sure to use the Gtk 
keyword so we can easily query for Gtk+ bugs

2.) Fixing bugs:
With Alp Toker we have a Gtk+ port reviewer and we have the lovely 
Apple team that is very helpful as well and can review your changes. We 
have Gtk+ people that can and will commit reviewed patches. Just follow 
this guideline[1] and you will make the world a better place.

thanks and I look forward to commit your patches.



Thanks Holger for this introduction to WebKit/GTK+ hacking! I'd also 
like to welcome contributors who want to help improve the 
platform-independent components of the GTK+ port like the Cairo graphics 
and HTTP backends, and future GStreamer video/audio support.

We have a competitive coverage of the SVG spec and the HTML5 canvas 
element, for example, but there are still basic gfx TODOs that anyone 
who has studied geometry at high school can help fix.

Such work will give us access to a large new correctness and performance 
test suite that can potentially assist the Cairo project itself.

Much of the Cairo graphics backend in WebKit is written using the Cairo 
C API directly so you don't have to re-learn the Cairo API through 
abstractions like Thebes (although it is abstracted higher up for use 
by the rendering engine).

webkit-dev mailing list

[webkit-dev] WTF license terms

2007-11-02 Thread Maciej Stachowiak

Hi everyone,

I'd like to change the license terms for the contents of  
JavaScriptCore/wtf from LGPL to Apple modified BSD, except for the  
copy of Google's TCMalloc and the unicode/ directory. All the  
copyrights on files besides tcmalloc and unicde are held by Apple and  
it looks like the only non-Apple contributions are a handful of  5  
line build fixes which were too small for copyright. Mainly I'd like  
to apply this to RefPtr, Vector, and the Hash-related classes.

I would like to do this to make the code usable by the widest possible  
range of projects, including even proprietary code, and open source  
projects with licenses that are not LGPL-compatible. This is basic  
data structure code, and although it is highly optimized it is not  
really specific to web browsing.

I wanted to run this proposed license change by the community. I know  
there have been some concerns about which code is BSD and which is  
LGPL. In this case, I think maximum reusability is the right thing for  
this code.


webkit-dev mailing list