> Jaffre does not need skeletons/stubs. The endpoints are pojos, parameters > and return values are java.io.Serializable objects. > > No registry is required. > > Jaffre Connectors listen well-defined ports that can easily be bound to a > specific address. They are firewall friendly. > > An experienced programmer will be able to fly over, and understand the whole > Jaffre code in less than an hour. > > Jaffre is intended to be easily customized.
OK, I'm sold on this project by this speech alone. +1 ;-) /Janne, who really wishes he could get back the hours he spent configuring RMI over the years --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org