On Jun 26, 2011, at 5:13 PM, David Jencks wrote: > BTW I noticed that the externalizable objects are all handled with > > externalizable.write(out) > > and the serializable ones > > out.writeObject(ser) > > rather than using > out.writeObject(ser) > > for all of them. Is this to save a little bit of overhead writing the class > definition etc?
Right. Essentially all the metadata for a class is boiled down to a byte, then what follows is pure data. In the absence of that, Java serialization tends to be the worst of both worlds (a text protocol and a binary protocol). -David >> On Jun 26, 2011, at 12:37 PM, David Jencks (JIRA) wrote: >> >>> >>> [ >>> https://issues.apache.org/jira/browse/OPENEJB-1616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13055156#comment-13055156 >>> ] >>> >>> David Jencks commented on OPENEJB-1616: >>> --------------------------------------- >>> >>> rev 1139925 separates dbcp datasources and References and actually works >>> with geronimo. >>> >>>> Allow more choice in sending datasources to clients over openejb jndi >>>> transport >>>> ------------------------------------------------------------------------------- >>>> >>>> Key: OPENEJB-1616 >>>> URL: https://issues.apache.org/jira/browse/OPENEJB-1616 >>>> Project: OpenEJB >>>> Issue Type: Improvement >>>> Components: server >>>> Affects Versions: 4.0 >>>> Reporter: David Jencks >>>> Assignee: David Jencks >>>> Fix For: 4.0 >>>> >>>> >>>> In geronimo we need to send global scope datasource definitions over the >>>> remote jndi connection to app clients. We can do this by using naming >>>> references. >>> >>> -- >>> This message is automatically generated by JIRA. >>> For more information on JIRA, see: http://www.atlassian.com/software/jira >>> >>> >>> >> >
