Hi Mochikiters, I'm working on an RPC (remote procedure call) system that'll run in a Java Enterprise Container. I'm using Mochikit (and parts of Prototype) to handle the front end interactions. This means I'm putting together a library of functions for wrapping up functions in stubs, etc.... and I was thinking of making it be a Mochikit.RPC object. It's behaviour is actually pretty limited in scope right now. There'll be a function for asking the server to create an object via a default constructor, and then another function for raising any signal to the object. There'll be some code to verify that each signal, and parameters are valid, etc... so the user sees an error in the browser when something bad happens, rather than gunk on the server. (Raising signals is analogous to calling methods, but in my application, I'm using mochikit to handle all the user event signals, and most code will be running on the server.)
I'm meeting with my boss today about opening the Java part as open source as well, but meanwhile, are you guys interested in something like this? IE, standardizing the formats, so this could be used to work on any server backend as well. You could write two server containers, one for java, one for python, and have two objects, one from each server, displayed in the browser. So any comments, suggestions, and ideas are appreciated Cheers, Yaakov --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "MochiKit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit -~----------~----~----~----~------~----~------~--~---
