[#TAVSERV-190] Gem: should use proper UUID classes instead of strings - myGrid

Details

Type: Improvement
Status: Resolved
Priority: Minor
Resolution: By Design
Affects Version/s: 2.2 alpha
Fix Version/s: Taverna 2.3 Server Release 1
Component/s: Ruby Gem
Labels:
None

Description

Currently UUIDs are passed about as strings. This is fine, but would probably be more robust if a UUID class was used instead.

Activity

Ascending order - Click to sort in descending order

Hide

Permalink

Robert Haines added a comment - 2011-12-07 18:04

Thinking about this, I'm not sure it makes a big difference. No UUID is created on the client side and we can assume that the server is generating valid UUIDs.

Leaving the UUIDs as strings on the client side would allow for the server side implementation of IDs to change and the client would still function correctly.

Show

Robert Haines added a comment - 2011-12-07 18:04 Thinking about this, I'm not sure it makes a big difference. No UUID is created on the client side and we can assume that the server is generating valid UUIDs. Leaving the UUIDs as strings on the client side would allow for the server side implementation of IDs to change and the client would still function correctly.

Hide

Permalink

Robert Haines added a comment - 2011-12-19 11:17

Having thought about this and discussed it I have decided that the UUIDs should be left as strings.

If the ID type changes in the future then it will continue to work transparently.

Show

Robert Haines added a comment - 2011-12-19 11:17 Having thought about this and discussed it I have decided that the UUIDs should be left as strings. If the ID type changes in the future then it will continue to work transparently.

People

Assignee:

Robert Haines

Reporter:

Robert Haines

Vote (0)

Watch (0)

Dates

Created:

2011-12-06 22:35

Updated:

2011-12-19 11:17

Resolved:

2011-12-19 11:17

Taverna Server

Gem: should use proper UUID classes instead of strings

Details

Description

Activity

People

Dates