river-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gregg Wonderly (JIRA)" <j...@apache.org>
Subject [jira] Commented: (RIVER-314) Enhanced codebase download
Date Thu, 16 Jul 2009 19:36:14 GMT

    [ https://issues.apache.org/jira/browse/RIVER-314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12732109#action_12732109

Gregg Wonderly commented on RIVER-314:

Some types of annotations that come to my mind are things like

@Preferred() to indicate that a class is to be preferred in any jar that it appears in.  This
would help automate the creation of a PREFERRED.LIST file.

@Prefer(classname) that would suggest that a particular class would be best suited to have
classname specified as preferred in the codebase that it is in.

The first case allows new code to be properly document, the second case allows 3rd-party or
old code to be externally documented.

I'm not sure if there is anything to do regarding boomerang objects

> Enhanced codebase download
> --------------------------
>                 Key: RIVER-314
>                 URL: https://issues.apache.org/jira/browse/RIVER-314
>             Project: River
>          Issue Type: New Feature
>            Reporter: Tom Hobbs
> Direct copy from the mailing list:
> "I'm also thinking that if we add support of compression to the http codebase (and serialization),
we can download individual class files over the network individually instead of entire jar
files (repeatedly compressed class files would be cached, to reduce CPU overhead).  This might
make performance a bit snappier when only requiring a few classes from a large library that
would normally be stored in a jar for instance."
> http://mail-archives.apache.org/mod_mbox/incubator-river-dev/200907.mbox/%3c4A5C8272.5070403@zeus.net.au%3e

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

View raw message