[
https://issues.apache.org/jira/browse/JUDDI-633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13742151#comment-13742151
]
Alex O'Ree commented on JUDDI-633:
----------------------------------
Avinash, I've already started porting the juddi client to .net. See
https://issues.apache.org/jira/browse/JUDDI-567
My opinion is that this should be implemented on the server, this way paging
operations would still function. This however would be a challenge due the fact
that tmodel values are stored as strings.
I've also discussed this same topic in my master's thesis, which discusses
improvements to UDDI. Comparison operators are suggested precisely for storing
QoS parameters, such as up time, throughput, response time, etc. Then a client
could ask for implements of service X that's sorted by response time, or only
has a response time less than 100ms or so. I'm going to go ahead and commit
what i have. It compiles, but its not complete
So due to the difficulty of doing this on the server, I'd suggest to use the
parse function to go from the tmodel's string value, to a number, then do your
own comparison. The query to UDDI should probably ask for services or binding
templates that have the specific tmodels that you're using for QoS parameters.
> Building a Find Qualifiers for comparison operator such as "greater then" and
> "less than".
> ------------------------------------------------------------------------------------------
>
> Key: JUDDI-633
> URL: https://issues.apache.org/jira/browse/JUDDI-633
> Project: jUDDI
> Issue Type: New Feature
> Components: juddi-tomcat
> Affects Versions: 3.1.5
> Environment: Windows 8 Pro.
> Tomcat 7.0
> MySQL 5.6
> Reporter: Avinash Ganpat Mahajan
> Assignee: Kurt T Stam
> Labels: features
> Fix For: 3.1.5
>
> Original Estimate: 1,224h
> Remaining Estimate: 1,224h
>
> I am trying to implement QoS aware UDDI searching mechanism.
> As QoS attributes are stored in KeyedReferences so needs to have some
> qualifiers to give flexibility for searching such as for cost.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
