Fine for that part - though a getBackend() would be useful.
You're right about singleton - we really want to use it as a factory class
for the peers rather than as a true singleton. We should definitely avoid
that term :-)
How about we follow the pattern Torque uses for the other generated
Oops, I used the swear word singleton ... Fortunately, I probably
misused it. I did not mean to enforce singleton behaviour, i.e. to forbid
the existence of more than one instance. The static wrapper would be for
ease of usage, the Backend class for those which do not want to use static
method
