January 2010 - infinispan-issues - Jboss List Archives

[JBoss JIRA] Created: (ISPN-172) Build a Java-based smart client that makes use of the HotRod protocol

by Manik Surtani (JIRA)

Build a Java-based smart client that makes use of the HotRod protocol --------------------------------------------------------------------- Key: ISPN-172 URL: https://jira.jboss.org/jira/browse/ISPN-172 Project: Infinispan Issue Type: Feature Request Components: Cache Server Reporter: Manik Surtani Assignee: Manik Surtani Fix For: 4.1.0.BETA1, 4.1.0.GA This will speak the HotRod protocol to communicate with the HotRod server module. Will be used as a reference implementation for clients in other languages as well so needs to be cleanly written and very well commented/documented. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 12 months

3
8
0 / 0

[JBoss JIRA] Created: (ISPN-243) Update developer wiki with Eclipse m2eclipse tips

by Galder Zamarreno (JIRA)

Update developer wiki with Eclipse m2eclipse tips ------------------------------------------------- Key: ISPN-243 URL: https://jira.jboss.org/jira/browse/ISPN-243 Project: Infinispan Issue Type: Task Reporter: Galder Zamarreno Assignee: Galder Zamarreno Fix For: 4.0.0.GA Update http://www.jboss.org/community/wiki/InfinispanQuickStartGuideforDevelopers with the following tips for Eclipse: - Do not use mvn eclipse:eclipse but instead of m2eclipse - Tips for m2eclipse: - Use external maven installation instead of embedded one, otherwise you might get some errors with regards to not understand the jre constraints in the pom.xml - Go to project's classpath and remove excludes for src/test/resources and src/main/resources, otherwise files in these folders won't be loaded and tests will fail. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

2
4
0 / 0

[JBoss JIRA] Created: (ISPN-161) REST API based on the server module as a back-end

by Manik Surtani (JIRA)

REST API based on the server module as a back-end ------------------------------------------------- Key: ISPN-161 URL: https://jira.jboss.org/jira/browse/ISPN-161 Project: Infinispan Issue Type: Feature Request Components: Cache Server Reporter: Manik Surtani Assignee: Manik Surtani Fix For: 4.1.0.BETA1, 4.1.0.CR1 Essentially, a module that can be deployed as a REST API to talk to the cache backend. Possibly something that wraps the cache, making use of libraries such as RESTEasy. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

2
7
0 / 0

[JBoss JIRA] Created: (ISPN-299) Implement an LIRS eviction policy

by Manik Surtani (JIRA)

Implement an LIRS eviction policy --------------------------------- Key: ISPN-299 URL: https://jira.jboss.org/jira/browse/ISPN-299 Project: Infinispan Issue Type: Feature Request Components: Eviction Reporter: Manik Surtani Assignee: Manik Surtani Fix For: 4.1.0.BETA1, 4.1.0.GA Need to investigate how this can be implemented in a thread-safe, and high-performing manner. Would probably make LRU obsolete. http://www.cse.ohio-state.edu/hpcs/WWW/HTML/publications/papers/TR-02-6.pdf -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

2
5
0 / 0

[JBoss JIRA] Created: (ISPN-171) Build a server module based on the HotRod protocol

by Manik Surtani (JIRA)

Build a server module based on the HotRod protocol -------------------------------------------------- Key: ISPN-171 URL: https://jira.jboss.org/jira/browse/ISPN-171 Project: Infinispan Issue Type: Feature Request Components: Cache Server Reporter: Manik Surtani Assignee: Manik Surtani Fix For: 4.1.0.BETA1, 4.1.0.GA Could be based on existing JBoss Remoting components which have the capability to handle load balancing and faoliver. Needs to share some components with ISPN-172 so that protocol parsing code isn't repeated. May also share some components with ISPN-173 so that abstract transport and socket handling code is reused. Will also need a comprehensive wiki page detailing usage and demonstration. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

2
5
0 / 0

[JBoss JIRA] Created: (ISPN-170) Design HotRod protocol

by Manik Surtani (JIRA)

Design HotRod protocol ---------------------- Key: ISPN-170 URL: https://jira.jboss.org/jira/browse/ISPN-170 Project: Infinispan Issue Type: Feature Request Components: Cache Server Reporter: Manik Surtani Assignee: Galder Zamarreno Fix For: 4.1.0.BETA1, 4.1.0.GA This is the new custom client/server binary protocol. Needs to support features to support the standard cache API, including: * failover * load balancing * piggyback server topology + consistent hash details used so that smart clients can be built * language-independent (no serialized Java objects!) Should be documented on the Infinispan wiki under design docs. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

2
5
0 / 0

[JBoss JIRA] Created: (ISPN-96) Generate configuration XSD schema and parse configuration XML files

by Vladimir Blagojevic (JIRA)

Generate configuration XSD schema and parse configuration XML files -------------------------------------------------------------------- Key: ISPN-96 URL: https://jira.jboss.org/jira/browse/ISPN-96 Project: Infinispan Issue Type: Task Affects Versions: 4.0.0.ALPHA4 Reporter: Vladimir Blagojevic Assignee: Vladimir Blagojevic Fix For: 4.0.0.BETA1 Currently we have a hand maintained XSD schema and manual processing/reading of XML configuration documents. If we introduce annotations for configuration elements we could automatically create XSD schema as well as automatically read XML configuration files. The end results is much less maintenance for configuration part of infinispan. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

2
6
0 / 0

[JBoss JIRA] Created: (ISPN-89) Document all configuration options available in XML and the Configuration beans on the wiki

by Manik Surtani (JIRA)

Document all configuration options available in XML and the Configuration beans on the wiki ------------------------------------------------------------------------------------------- Key: ISPN-89 URL: https://jira.jboss.org/jira/browse/ISPN-89 Project: Infinispan Issue Type: Task Components: Configuration Reporter: Manik Surtani Assignee: Galder Zamarreño Fix For: 4.0.0.GA This used to be in the User Guide of JBC, and now since we don't have a User Guide and everything is maintained on the wiki, we need a table on the wiki. Perhaps something that looks like this: http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs... Should explain each XML element, attribute, allowed values, default values, and equivalent setter in the Configuration bean. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

3
15
0 / 0

[JBoss JIRA] Created: (ISPN-97) Improve configuration processing and maintenance

by Vladimir Blagojevic (JIRA)

Improve configuration processing and maintenance ------------------------------------------------ Key: ISPN-97 URL: https://jira.jboss.org/jira/browse/ISPN-97 Project: Infinispan Issue Type: Task Affects Versions: 4.0.0.ALPHA4 Reporter: Vladimir Blagojevic Assignee: Vladimir Blagojevic Fix For: 4.0.0.BETA1 In order to improve configuration processing and maintenance we have to use Java annotations. We could keep all current configuration beans, that is all subclasses of AbstractConfigurationBean but introduce annotation(s) for those beans that would: - annotate each bean setter with a reference to the XML element in question (full path to it - e.g., infinispan/namedCache/cluster/sync) - provide default configuration value - describe human readable documentation for each configuration option in plain english - references to classes to process certain complex elements and others as the need arise. Furthermore we could also: - remove current hand maintained schema - create schema by automated tools given metadata in annotations - create all human readable documentation from these annotations for manuals. wiki etc etc - read all configuration elements from xml configuration files using metadata in annotations thus avoiding "by hand" reading we have now -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

2
6
0 / 0

[JBoss JIRA] Created: (ISPN-304) REST API should not use POST

by Jozef Hartinger (JIRA)

REST API should not use POST ---------------------------- Key: ISPN-304 URL: https://jira.jboss.org/jira/browse/ISPN-304 Project: Infinispan Issue Type: Bug Components: Cache Server Affects Versions: 4.0.0.CR2 Reporter: Jozef Hartinger Assignee: Manik Surtani Priority: Optional Fix For: 4.0.0.CR3 Currently, the REST API provided by Infinispan uses POST for creating new resources, for example: POST to /infinispan/rest/data/foo containing "bar" will create a new key-value pair (foo, bar) However, the HTTP spec says that POST should be used for creating *subordinate* resources, which is not done in this case because the resource itself is created and not a subordinate one. Moreover, the RESTful Web Services book which is kind of a bible for writting RESTful applications claims that the POST method can be used for creating resources *only if the server is in charge of choosing the URI for a new resource* (for example if a POST sent to /infinispan/rest/data would cause server to choose a key for the given value and make it available under /infinispan/rest/data/choosenKey). In contrast, if the *client is responsible for creating the URI* (which is the case of Infinispan), the client should use a PUT sent to the chosen URI (PUT /infinispan/rest/data/foo) to create the resource. That means that there is no difference between the initial creation of a resource and a subsequent update (both request are PUT requests to the same URI) - fits exactly how cache.put() works. The downside of this approach is that the client does not get 409 when he/she tries to overwrite an existing value. Nevertheless, if this behavior is really needed, it can be achieved alternatively, for example by introducing a path parameter "overwrite" which if set to "false" and the resource already exists, will cause the server to return 409. To summarize, IMHO it would be cleaner to stop using POST for creating new cache records and use PUT for this purpose instead. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

3
14
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues January 2010