You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@river.apache.org by "Mark Brouwer (JIRA)" <ji...@apache.org> on 2007/01/11 22:39:27 UTC

[jira] Created: (RIVER-6) com.sun.jini.tool.ClassServer needs support for Last-Modified and If-Modified-Since headers

com.sun.jini.tool.ClassServer needs support for Last-Modified and If-Modified-Since headers
-------------------------------------------------------------------------------------------

                 Key: RIVER-6
                 URL: https://issues.apache.org/jira/browse/RIVER-6
             Project: Apache River
          Issue Type: Improvement
            Reporter: Mark Brouwer
            Priority: Minor


Given the fact ClassServer is the number one codebase server in the world one might expect it to provide a bit more support for the response header {{Last-Modified}} and the request header {{If-Modified-Since}}.

While the lack of these might not be very harmfull for JVMs that have the default {{jar}} protocol handler, some containers providing a more advanced caching mechanism for JAR files can make effective use of these headers. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Updated: (RIVER-6) com.sun.jini.tool.ClassServer needs support for Last-Modified and If-Modified-Since headers

Posted by "Mark Brouwer (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/RIVER-6?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mark Brouwer updated RIVER-6:
-----------------------------

          Component/s: com_sun_jini_tool
    Affects Version/s: jtsk_2.1

> com.sun.jini.tool.ClassServer needs support for Last-Modified and If-Modified-Since headers
> -------------------------------------------------------------------------------------------
>
>                 Key: RIVER-6
>                 URL: https://issues.apache.org/jira/browse/RIVER-6
>             Project: River
>          Issue Type: Improvement
>          Components: com_sun_jini_tool
>    Affects Versions: jtsk_2.1
>            Reporter: Mark Brouwer
>            Priority: Minor
>
> Given the fact ClassServer is the number one codebase server in the world one might expect it to provide a bit more support for the response header {{Last-Modified}} and the request header {{If-Modified-Since}}.
> While the lack of these might not be very harmfull for JVMs that have the default {{jar}} protocol handler, some containers providing a more advanced caching mechanism for JAR files can make effective use of these headers. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (RIVER-6) com.sun.jini.tool.ClassServer needs support for Last-Modified and If-Modified-Since headers

Posted by "Dan Creswell (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/RIVER-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12464138 ] 

Dan Creswell commented on RIVER-6:
----------------------------------

Couple of things I think we should maybe consider:

(1)  Do any other webservers already provide support for this?  Jetty?  Apache httpd?  Others?

(2)  Should we consider migrating away from ClassServer over time to one of those servers in (1)?

It does seem to me that ClassServer is a good "get you started" option which we might wish to keep but, for "more advanced" deployments, perhaps we should be incorporating or relying on a well-maintained package from elsewhere.  How much value is there in maintaining our own httpd?



> com.sun.jini.tool.ClassServer needs support for Last-Modified and If-Modified-Since headers
> -------------------------------------------------------------------------------------------
>
>                 Key: RIVER-6
>                 URL: https://issues.apache.org/jira/browse/RIVER-6
>             Project: Apache River
>          Issue Type: Improvement
>            Reporter: Mark Brouwer
>            Priority: Minor
>
> Given the fact ClassServer is the number one codebase server in the world one might expect it to provide a bit more support for the response header {{Last-Modified}} and the request header {{If-Modified-Since}}.
> While the lack of these might not be very harmfull for JVMs that have the default {{jar}} protocol handler, some containers providing a more advanced caching mechanism for JAR files can make effective use of these headers. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Commented: (RIVER-6) com.sun.jini.tool.ClassServer needs support for Last-Modified and If-Modified-Since headers

Posted by "Holger Hoffstätte (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/RIVER-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12524797 ] 

Holger Hoffstätte commented on RIVER-6:
---------------------------------------

Also, keep in mind that JDK6 contains a HTTP server by default, though I don't know if it supports those headers and/or could be used.


> com.sun.jini.tool.ClassServer needs support for Last-Modified and If-Modified-Since headers
> -------------------------------------------------------------------------------------------
>
>                 Key: RIVER-6
>                 URL: https://issues.apache.org/jira/browse/RIVER-6
>             Project: River
>          Issue Type: Improvement
>          Components: com_sun_jini_tool
>    Affects Versions: jtsk_2.1
>            Reporter: Mark Brouwer
>            Priority: Minor
>
> Given the fact ClassServer is the number one codebase server in the world one might expect it to provide a bit more support for the response header {{Last-Modified}} and the request header {{If-Modified-Since}}.
> While the lack of these might not be very harmfull for JVMs that have the default {{jar}} protocol handler, some containers providing a more advanced caching mechanism for JAR files can make effective use of these headers. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.