Hi What do you all think of this. I have an external component to my app server. The component is written in C++ but has a java interface to it. So i am thinking i wrapping the component up in a serversocket. Then i create a URL resource factory that accesses this component. Then i create a stateless session bean that accesses this URL via a JNDI lookup. Then i kind of have my own protocol for communicating with the component. I write some parameters to the URL output stream the component does its stuff then the read the corresponding parameters from the URL input stream. I personally think this is a nice lightwight solution to solving this problem... However does anyone think i have over looked something. By the way the C++ component is supposed to be thread safe. Other solutions i have been looking at are CORBA and JMS but does anyone think they are over kill. All the component does is, i pass it some parameters and it returns me some other ids that represent ids in the database. regards Pete =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
