© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
The point of bug 118737 is that we also need a structured or systematic way to send the exception parameters across the wire.
Exceptions that are likely to be caught and interpreted by the proxy Remote object, may need to be interpreted by examining their parameters, like the path of the affected file.
It's not easy to pass across parameters that might refer to other in-memory objects, but in most cases we only care about strings. (Should check)
Most Bazaar exceptions construct their string form on demand based on the parameters. If we're going to reconstruct a real new exception on the client, we presumably need to pass all the parameters used in the string template - this seems cleaner anyhow.