Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

master branch tODE should use STON v0.5 #174

Closed
dalehenrich opened this issue Jun 19, 2015 · 1 comment
Closed

master branch tODE should use STON v0.5 #174

dalehenrich opened this issue Jun 19, 2015 · 1 comment
Milestone
0.0.4

Comments

@dalehenrich
Copy link
Owner

The UTF8 handling in v0.5 and used by TODE is not quite correct ... the string fields should not be individually encoded (as they are in v0.5), instead the entire STON string should be encoded as UTF8 .... The pharo version of STON does not have this special UTF8 handling as I added it for tODE ... I misunderstood the issues for utf8 until i did some work on NeoJSON. I am in the process of fixing the encoding problem and porting SON v0.9 to GemStone ... the current dev branch of tODE will start using STON v0.9 and the different encoding scheme. At that point the pharo client should use the standard version of STON for pharo as well.
dalehenrich added a commit that referenced this issue Jun 19, 2015
@dalehenrich
Issue #174: use STON v0.5 for GemStone
202af6e
@dalehenrich dalehenrich mentioned this issue Jun 19, 2015
Closed
@dalehenrich
Copy link
Owner Author

in the near term the dev branch will use STON v0.5.1 until Issue #175 is complete

dalehenrich added a commit that referenced this issue Jun 19, 2015
@dalehenrich
Issue #174: Use a tagged version of STON (v0.5.? --> 0.5.1 right now)
3b7739e
@dalehenrich dalehenrich mentioned this issue Jun 19, 2015
Merged
@dalehenrich dalehenrich added this to the 0.0.3 milestone Jun 19, 2015
dalehenrich added a commit that referenced this issue Jun 23, 2015
@dalehenrich
Issue #174: use STON v0.5 for pharo branch (dalehenrich/ston pharo-0.…
fe286f2 
…5 tag)
@dalehenrich dalehenrich modified the milestones: 0.0.3, 0.0.4 Jun 23, 2015
@dalehenrich dalehenrich mentioned this issue Jun 23, 2015
Merged
dalehenrich added a commit that referenced this issue Jun 23, 2015
@dalehenrich
Issue #174: Use a tagged version of STON for pharo branch: pharo-0.5.?
d22029e
dalehenrich added a commit that referenced this issue Jun 23, 2015
@dalehenrich
Issue #174: fix github version for STON pharo branch
f0538e8
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
0.0.4
Development

No branches or pull requests
1 participant
@dalehenrich