posted 23 years ago
Alan,
What I needed to do was have Cold Fusion receive a couple thousand bytes via http, and pass that data to my Java application. Since I needed to get the data into the file system anyway, I let Cold Fusion write the file and just pass the file name over to the Java application. In my application I had a FIFOQueue class, which I implemented by extending LinkedList. It was an object of that class that I made visible to Cold Fusion by using RMI to tie together the separate JVM's. That approach worked fine, although I never went out of my way to try to stress it.
In the end, I decided that I wanted my queues to have persistence in case something went awry at an inopportune time. I also didn't want my Java application to necessarily be running when data came in over HTTP. So, I now let Cold Fusion write not only the data file, but also write the queue entry to a database. Then, the Java application picks up queued entries from the database. So, RMI is now out of the picture, and both the data file and the queue entry are 'safe stored' at the earliest possible time.
Ron