State Replication Protocol (SRP)

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

State Replication Protocol (SRP)

Runar Jordahl
"State Replication Protocol (SRP) is a multi-dialect framework for binary
serialization of object state." SRP seems to have functionality that
is not found in BOSS.

SRP can be loaded from the public Store DB:
http://www.cincomsmalltalk.com/publicRepository/PlbStateReplicationProtocol.html
http://www.cincomsmalltalk.com/publicRepository/SrpPortableObjectRepresentations.html
http://www.cincomsmalltalk.com/publicRepository/SrpTests.html

The code has not been updated since 2004 on the public Store DB. Is it
so that this framework is no longer maintained?
Is the version on the public Store DB kept up with the latest version
of SRP for other dialects?
Is anyone still using SRP?

Read more about SRP here:
http://www.ccse.kfupm.edu.sa/~sohel/IMPP/references/About+State+Replication+Protocol+(SRP).html
http://www.whysmalltalk.com/Smalltalk_Solutions/sts2004/pdf/Baumann.pdf

Does anyone have more documentation than the pages I mention?

Kind regards
Runar

Reply | Threaded
Open this post in threaded view
|

Re: State Replication Protocol (SRP)

Joachim Geidel
Runar,

> Is anyone still using SRP?

I know of one active project which has been using it for years and still
does so. They are using VW 7.4.1.

Joachim

Reply | Threaded
Open this post in threaded view
|

RE: State Replication Protocol (SRP)

Paul Baumann
In reply to this post by Runar Jordahl
SRP has value in many regards but it hasn't been promoted. The market
niche for efficient binary portability is very small. Most people tend
to use non-portable binary serialization that comes with their ST
dialect or they use XML when efficiency isn't critical. I haven't
touched the code for several years. It is released under a license where
anyone is welcome to take it over.

The version published to the public StORE dB may be an early release.
Code had been posted on SourceFORGE (http:/sourceforge.net/projects/srp)
and most recently at StS when it was held in Seattle. The version at StS
was distributed on CD and published to a URL that is now dead. I'd have
to dig up the code myself. I recall working on an off-by-one encoding
bug in some of the most recent versions (perhaps not released though).
Sorry, I lost interest in the project after it was finished and given
away. If you are looking for additional documentation then look for
class-side methods named #documentation.

Paul Baumann

-----Original Message-----
From: Runar Jordahl [mailto:[hidden email]]
Sent: Tuesday, March 13, 2007 1:04 PM
To: VWNC,
Subject: State Replication Protocol (SRP)

"State Replication Protocol (SRP) is a multi-dialect framework for
binary serialization of object state." SRP seems to have functionality
that is not found in BOSS.

SRP can be loaded from the public Store DB:
http://www.cincomsmalltalk.com/publicRepository/PlbStateReplicationProto
col.html
http://www.cincomsmalltalk.com/publicRepository/SrpPortableObjectReprese
ntations.html
http://www.cincomsmalltalk.com/publicRepository/SrpTests.html

The code has not been updated since 2004 on the public Store DB. Is it
so that this framework is no longer maintained?
Is the version on the public Store DB kept up with the latest version of
SRP for other dialects?
Is anyone still using SRP?

Read more about SRP here:
http://www.ccse.kfupm.edu.sa/~sohel/IMPP/references/About+State+Replicat
ion+Protocol+(SRP).html
http://www.whysmalltalk.com/Smalltalk_Solutions/sts2004/pdf/Baumann.pdf

Does anyone have more documentation than the pages I mention?

Kind regards
Runar
 
 
 
--------------------------------------------------------
This message may contain confidential information and is intended for specific recipients unless explicitly noted otherwise. If you have reason to believe you are not an intended recipient of this message, please delete it and notify the sender. This message may not represent the opinion of IntercontinentalExchange, Inc. (ICE), its subsidiaries or affiliates, and does not constitute a contract or guarantee. Unencrypted electronic mail is not secure and the recipient of this message is expected to provide safeguards from viruses and pursue alternate means of communication where privacy or a binding message is desired.