You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Eugene Kuleshov (JIRA)" <ji...@apache.org> on 2007/04/26 02:09:15 UTC
[jira] Created: (WICKET-505) Show server information in the Web UI
for wicket-examples
Show server information in the Web UI for wicket-examples
---------------------------------------------------------
Key: WICKET-505
URL: https://issues.apache.org/jira/browse/WICKET-505
Project: Wicket
Issue Type: New Feature
Components: wicket-examples
Affects Versions: 1.3
Reporter: Eugene Kuleshov
Show server information in the Web UI for wicket-examples. The primary use case for this is to see server name when running wicket-examples on clustered environment. It could be as simple as allow to specify some system property for the server name.
Also it may be also useful to have a link to other cluster nodes, so user can jump between them and see that data are distributed. Alternative approach could be to run some kind of round-robin proxy between web browser and the cluster nodes with could randomly bounce requests between nodes.
This will be useful for purposes of demo and performance testing.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (WICKET-505) Show server information in the Web
UI for wicket-examples
Posted by "Eugene Kuleshov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491865 ]
Eugene Kuleshov commented on WICKET-505:
----------------------------------------
Igor, the main point of this request is not about clustering, but about some way to see what server/node (i.e. some symbolic name) standard Wicket examples are running at. So, they can be used out of the box for deployment without building custom code.
> Show server information in the Web UI for wicket-examples
> ---------------------------------------------------------
>
> Key: WICKET-505
> URL: https://issues.apache.org/jira/browse/WICKET-505
> Project: Wicket
> Issue Type: New Feature
> Components: wicket-examples
> Affects Versions: 1.3
> Reporter: Eugene Kuleshov
>
> Show server information in the Web UI for wicket-examples. The primary use case for this is to see server name when running wicket-examples on clustered environment. It could be as simple as allow to specify some system property for the server name.
> Also it may be also useful to have a link to other cluster nodes, so user can jump between them and see that data are distributed. Alternative approach could be to run some kind of round-robin proxy between web browser and the cluster nodes with could randomly bounce requests between nodes.
> This will be useful for purposes of demo and performance testing.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (WICKET-505) Show server information in the Web UI
for wicket-examples
Posted by "Igor Vaynberg (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Igor Vaynberg resolved WICKET-505.
----------------------------------
Resolution: Fixed
Fix Version/s: 1.3
> Show server information in the Web UI for wicket-examples
> ---------------------------------------------------------
>
> Key: WICKET-505
> URL: https://issues.apache.org/jira/browse/WICKET-505
> Project: Wicket
> Issue Type: New Feature
> Components: wicket-examples
> Affects Versions: 1.3
> Reporter: Eugene Kuleshov
> Assigned To: Eelco Hillenius
> Fix For: 1.3
>
>
> Show server information in the Web UI for wicket-examples. The primary use case for this is to see server name when running wicket-examples on clustered environment. It could be as simple as allow to specify some system property for the server name.
> Also it may be also useful to have a link to other cluster nodes, so user can jump between them and see that data are distributed. Alternative approach could be to run some kind of round-robin proxy between web browser and the cluster nodes with could randomly bounce requests between nodes.
> This will be useful for purposes of demo and performance testing.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (WICKET-505) Show server information in the Web
UI for wicket-examples
Posted by "Eelco Hillenius (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491875 ]
Eelco Hillenius commented on WICKET-505:
----------------------------------------
Eugene, I added a little toy to the wicket-examples project/ linkomatic. See org.apache.wicket.examples.ServerHostNameAndTimeFilter which is configured in LinkomaticApplication like this:
protected void init()
{
// log host name and server time in the browser's status bar
getRequestCycleSettings().addResponseFilter(new ServerHostNameAndTimeFilter());
}
Would this work for you?
> Show server information in the Web UI for wicket-examples
> ---------------------------------------------------------
>
> Key: WICKET-505
> URL: https://issues.apache.org/jira/browse/WICKET-505
> Project: Wicket
> Issue Type: New Feature
> Components: wicket-examples
> Affects Versions: 1.3
> Reporter: Eugene Kuleshov
>
> Show server information in the Web UI for wicket-examples. The primary use case for this is to see server name when running wicket-examples on clustered environment. It could be as simple as allow to specify some system property for the server name.
> Also it may be also useful to have a link to other cluster nodes, so user can jump between them and see that data are distributed. Alternative approach could be to run some kind of round-robin proxy between web browser and the cluster nodes with could randomly bounce requests between nodes.
> This will be useful for purposes of demo and performance testing.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (WICKET-505) Show server information in the Web
UI for wicket-examples
Posted by "Igor Vaynberg (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491860 ]
Igor Vaynberg commented on WICKET-505:
--------------------------------------
since the examples project isnt clustered what good is it putting there? there is nothing needed in the core to do this, it can be completely done by the user - there are 10 different ways to setup clusters, do we need to build support for each one? nodename, nodename+context name, nodename+port+context name, etc, etc, etc.
> Show server information in the Web UI for wicket-examples
> ---------------------------------------------------------
>
> Key: WICKET-505
> URL: https://issues.apache.org/jira/browse/WICKET-505
> Project: Wicket
> Issue Type: New Feature
> Components: wicket-examples
> Affects Versions: 1.3
> Reporter: Eugene Kuleshov
>
> Show server information in the Web UI for wicket-examples. The primary use case for this is to see server name when running wicket-examples on clustered environment. It could be as simple as allow to specify some system property for the server name.
> Also it may be also useful to have a link to other cluster nodes, so user can jump between them and see that data are distributed. Alternative approach could be to run some kind of round-robin proxy between web browser and the cluster nodes with could randomly bounce requests between nodes.
> This will be useful for purposes of demo and performance testing.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (WICKET-505) Show server information in the Web
UI for wicket-examples
Posted by "Igor Vaynberg (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491867 ]
Igor Vaynberg commented on WICKET-505:
--------------------------------------
ah, i see. so you want to cluster the examples project itself, not do this for your application. cool with me.
> Show server information in the Web UI for wicket-examples
> ---------------------------------------------------------
>
> Key: WICKET-505
> URL: https://issues.apache.org/jira/browse/WICKET-505
> Project: Wicket
> Issue Type: New Feature
> Components: wicket-examples
> Affects Versions: 1.3
> Reporter: Eugene Kuleshov
>
> Show server information in the Web UI for wicket-examples. The primary use case for this is to see server name when running wicket-examples on clustered environment. It could be as simple as allow to specify some system property for the server name.
> Also it may be also useful to have a link to other cluster nodes, so user can jump between them and see that data are distributed. Alternative approach could be to run some kind of round-robin proxy between web browser and the cluster nodes with could randomly bounce requests between nodes.
> This will be useful for purposes of demo and performance testing.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (WICKET-505) Show server information in the Web
UI for wicket-examples
Posted by "Eelco Hillenius (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491855 ]
Eelco Hillenius commented on WICKET-505:
----------------------------------------
Besides the obvious option of adding components for that, we could show the server with a IResponseFilter, much like ServerAndClientTimeFilter works now
> Show server information in the Web UI for wicket-examples
> ---------------------------------------------------------
>
> Key: WICKET-505
> URL: https://issues.apache.org/jira/browse/WICKET-505
> Project: Wicket
> Issue Type: New Feature
> Components: wicket-examples
> Affects Versions: 1.3
> Reporter: Eugene Kuleshov
>
> Show server information in the Web UI for wicket-examples. The primary use case for this is to see server name when running wicket-examples on clustered environment. It could be as simple as allow to specify some system property for the server name.
> Also it may be also useful to have a link to other cluster nodes, so user can jump between them and see that data are distributed. Alternative approach could be to run some kind of round-robin proxy between web browser and the cluster nodes with could randomly bounce requests between nodes.
> This will be useful for purposes of demo and performance testing.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (WICKET-505) Show server information in the Web UI
for wicket-examples
Posted by "Eelco Hillenius (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eelco Hillenius reassigned WICKET-505:
--------------------------------------
Assignee: Eelco Hillenius
> Show server information in the Web UI for wicket-examples
> ---------------------------------------------------------
>
> Key: WICKET-505
> URL: https://issues.apache.org/jira/browse/WICKET-505
> Project: Wicket
> Issue Type: New Feature
> Components: wicket-examples
> Affects Versions: 1.3
> Reporter: Eugene Kuleshov
> Assigned To: Eelco Hillenius
>
> Show server information in the Web UI for wicket-examples. The primary use case for this is to see server name when running wicket-examples on clustered environment. It could be as simple as allow to specify some system property for the server name.
> Also it may be also useful to have a link to other cluster nodes, so user can jump between them and see that data are distributed. Alternative approach could be to run some kind of round-robin proxy between web browser and the cluster nodes with could randomly bounce requests between nodes.
> This will be useful for purposes of demo and performance testing.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.