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

dev branch should use STON v0.9.* (encode/decode full STON string) #175

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

dev branch should use STON v0.9.* (encode/decode full STON string) #175

dalehenrich opened this issue Jun 19, 2015 · 1 comment

Comments

@dalehenrich
Copy link
Owner

As a complement to Issue #174, the dev branch needs to be changed with respect to how utf8 encoding is done in STON ... will also need to be properly coordinated between client and server
@dalehenrich dalehenrich mentioned this issue Jun 19, 2015
Closed
@dalehenrich
Copy link
Owner Author

  • First convert dev branch to use STON v0.9 v0.5
    • v0.5 on master branch (current - v0.0.3)
    • pharo-0.5 on master branch for pharo (current - v0.0.4)
    • v0.5.? on dev branch (current)
    • pharo-0.5.? dev branch for pharo (current)
    • v0.9.0 on dev branch (soon)
    • pharo-0.9.0 pharo branch (soon)
  • Next switch encoding scheme in STON and tag as STON v0.9.*
  • Change tODE to use STON v0.9.* and merge to dev branch
  • Change tODE so that client and server negotiate which object serialization scheme to use
    • this way old clients can communicate with new servers and new clients can communicate with old servers ... there was nothing technically wrong with the old way, but the new way is more efficient, readable arguably more correct

dalehenrich added a commit that referenced this issue Jun 22, 2015
@dalehenrich
Issue #175: a little too aggressive in removing methods
10552b9
dalehenrich added a commit that referenced this issue Jun 22, 2015
@dalehenrich
Issue #175: use STON v0.9
5018296
@dalehenrich dalehenrich mentioned this issue Jun 22, 2015
Merged
@dalehenrich dalehenrich changed the title dev branch should use STON v0.9.1 (encode/decode full STON string) dev branch should use STON v0.9.* (encode/decode full STON string) Jun 25, 2015
dalehenrich added a commit that referenced this issue Jun 25, 2015
@dalehenrich
Issue #175: major edit to start using the new protocol introduced in …
1e91a4e 
…STON v0.9.? and pharo-0.9.1?. v0.9.1 and pharo-0.9.1 are on the gemstone_dev and pharo_dev branches so that travis tests can be run ...

encoding scheme is still the same as older versions of STON...
dalehenrich added a commit that referenced this issue Jun 25, 2015
@dalehenrich
Issue #175: need to update Metacello to be able to load tag pattern
2edf71f
dalehenrich added a commit that referenced this issue Jun 25, 2015
@dalehenrich
Issue #175: fix a typo and baseline error
71d849a
dalehenrich added a commit that referenced this issue Jun 26, 2015
@dalehenrich
Issue #175: TodeCommunicationProtocol and friends added as better opt…
5e0f14d 
…ion for managing changes and upgrades to object serialization ... need to have a handshake between client and server to settle on the version of STON to be used and someday may use something other than STON ...
dalehenrich added a commit that referenced this issue Jun 26, 2015
@dalehenrich
Issue #175: rename the classes
684a06e
dalehenrich added a commit that referenced this issue Jun 26, 2015
@dalehenrich
Issue #175: checkpoint client-side changes for TodeObjectSerializer
3182466
dalehenrich added a commit that referenced this issue Jun 26, 2015
@dalehenrich
Issue #175: convert all users of STON in tODE to use #objectSerialize…
1f589ad 
…r method
dalehenrich added a commit that referenced this issue Jun 26, 2015
@dalehenrich
Issue #175: convert client-side code to use #objectSerializer
9965ba7
dalehenrich added a commit that referenced this issue Jun 26, 2015
@dalehenrich
Issue #175: enable client-side objectSerialization and disable use of…
31c76b3 
… 0.9.1, so we can

- strip out 0.9.1 hacks
- implement 0.5.1 compat (pluggalble old-style encoding)
- implement the REAL 0.9.1
  - hex chars trigger old-style encoding
  - no hex char encoding at all
- tests, tests and tests
@dalehenrich dalehenrich mentioned this issue Jun 26, 2015
Closed
dalehenrich added a commit that referenced this issue Jun 29, 2015
@dalehenrich
Issue #175: convert to using 091 serializer ... add some tests ... 05…
d0d0698 
…1 serializer not converted to new scheme yet
dalehenrich added a commit that referenced this issue Jun 29, 2015
@dalehenrich
Issue #175: put TodeObjectSerializer with new (0.9.3) implementation …
0371c08 
…of STON...
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
No milestone
Development

No branches or pull requests
1 participant
@dalehenrich