Tasks #1946

Refactor 'send' method of informer to 'publish'

Added by Anonymous over 7 years ago. Updated over 6 years ago.

Status:ResolvedStart date:08/21/2014
Priority:NormalDue date:
Assignee:-% Done:

100%

Category:Java
Target version:rsb-0.13

Description

I suggest refactoring the 'send' methods to 'publish' in the java and common-lisp implementations of the informer to conform to the naming in rsb-cpp and rsb-python. (or vice-versa)


Related issues

Related to Robotics Service Bus - Bug #2222: Remove differences between APIs Resolved 04/14/2015

History

#1 Updated by Anonymous over 6 years ago

  • Related to Bug #2222: Remove differences between APIs added

#2 Updated by J. Moringen over 6 years ago

  • Target version changed from rsb-0.12 to rsb-0.13

#3 Updated by J. Wienke over 6 years ago

  • Category set to Common Lisp
  • Status changed from New to Resolved
  • Assignee set to J. Moringen
  • % Done changed from 0 to 50

For java, this has been done with the changes in #2222. CL is missing.

#4 Updated by J. Moringen over 6 years ago

  • Category changed from Common Lisp to Java
  • Assignee deleted (J. Moringen)
  • % Done changed from 50 to 100

In the CL implementation, send is a generic function, not a method of/in the informer class. There are methods on the send function for different kinds of participants and "publish" would not be an appropriate name in all cases.

There could be an additional dedicated publish function which would only be applicable to informer objects, but that would increase the potential confusion instead in my opinion.

#5 Updated by J. Moringen over 6 years ago

Btw, to really go through with this change, the terminology used in the manual (E.g. Examples » Basic Communication » {Sending Data,Receiving Data} has to be changed as well.

Also available in: Atom PDF