Need a way to allow the protocol to change over time
Brought to you by:
zer0wing
Menu
▾
▴
#25 Need a way to allow the protocol to change over time
As of right now, if you define a protocol, then thats the
protocol your stuck with. RAMP needs a way to specify
that a new version of the protocol is available, or that
previous types of messages are depricated.
Some scheme needs to be in place to allow a protocol to
be refactored after its already being used by the system.
Logged In: YES
user_id=318102
One solution would be to allow messages to have a
"depricated" attribute. This would let the protocol
designer to depricate a message and eventually remove it.
It should only be possible to to this on server messages.
This does mean that the protocol will have to have some
standard messages to work with so that the server can always
send back a "depricated message" and warn the client that
the protocol they are using is beginning to go out of date.