ChangeRequest #93

Ignore missing classes on remote objects

Added by Noctarius over 7 years ago. Updated over 5 years ago.

Status:RejectedStart date:05/09/2011
Priority:NormalDue date:
Assignee:achristian% Done:

100%

Category:Core
Target version:1.2.0

Description

Whi9le loading remote object (by either interface- or standard-lookup) missing clientside interfaces should be ignored and skipped out, since at clientside a service implementation should be able tp feature more than one api set to bind multiple kind of clients.

simon_class_patch.patch Magnifier (4.74 KB) Noctarius, 05/09/2011 08:05 AM

History

#1 Updated by achristian over 7 years ago

  • Tracker changed from Bug to ChangeRequest
  • Status changed from New to Assigned
  • Assignee set to achristian

#2 Updated by achristian over 7 years ago

  • Category set to Core
  • Target version set to 1.2.0

#3 Updated by achristian over 5 years ago

  • Status changed from Assigned to Rejected
  • % Done changed from 0 to 100

After more than 2 years, finally found some time to check this. Results:

  1. Noone else requestes this feature --> not really required?
  2. Just skipping an interface because of "could ne be loaded" is surely not enough. Who decides which interface IS actually required? Also this feature will complicate programming faults on client-side (forgot to add interface or something like this).

From my point of view: If there are different clients: Create different remote objects (or wrappers), which should not be too complicated thanks to the simon remote annotation.

Also available in: Atom PDF