I am using DOM4j (from sourceforge) and am using a SAXReader to read a String from an input Stream. The Sax Reader will only close on an EOF or closing the socket.
Due to the nature of my program I cannot close the socket. How can I send an EOF to my server app from a client to indicate the end of file condition without closing the socket.
I.e.: The client reads an XML file line by line and sends it to the server. The server is reading the file via a SAXReader. I need to indicate the EOF condition to the server from the client. How do I achieve this.
Sending a String and then parsing it is not an option due to the size of the XML files.
TIA
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
If the XML files are so large then why not just send them on seperate connections? The preformance loss should be negligible if the files are huge.
Otherwise you will need to implement a seperate protocol which supports marking the seperate XML file. Your server would then need to parse this protocol, streaming each XML files data to your sax reader.
The files could, potentialy, grow to be in the hundreds of Megabytes with multiple users. Reading in as a Strings and then parsing into the SAX reader is an option I would rather not have to take, so implementing a protocol would be a last option.
As to the seperate connections, the application will initilay have peaks of 1000+ users in a 5 minute interval and eventualy scale to tens of thousands of transactions per minute.
The application is composed of an RMI server (broker server) which will serve multiple listener servers (MQ, IIOP and Socket servers). I.e.: A client will use one of these listener servers to access the broker server. The broker server will then open multiple connections to other servers.
The server will eventualy open multiple connections over diffrent middlwares, (MQ, Tibco, IIOP, JDBC, etc.) for each client and broker transactions over a mixed legacy integration environment. (Several of the integrated legacy applications run over flat files). Performance issues and scalability are critical to the success of the project. Connections are massivley pooled to allow for scalability so opening more connections for the socket listener server is going to impact on both performance and scalability.
So, a transaction woul be defined as opening a connection to one of the listener servers, sending a variable sized (usualy large) XML file to the listener. Parsing the file into a DOM tree, passing the tree to the broker server, have the broker translate the DOM tree to one ore more middlwares, broker a transaction over multiple legacy applications, read the reply from the multiple Legacy applications using multiple middleware protocols, translate back to a DOM Tree, send the XML file back to the listener server and have the listener server print the tree back to the client.
The entire platform is now up except for the socket version of the listener server.
To complicate things, the application has to run on the customers mainframe which is already handling several thousand transactions per minute for other applications, so connections, memory and threads are at a premium.
Have you attempted to clone an InputStream, and would closing the clone cause the EOF?
Do you have any suggestions as to how to minimize the number of connections, preferably without using Strings or byte arrays?
:-)
http://www.evalu8.com.au
"Giving everyone a voice"
Business Accounts
Answer for Membership
by: objectsPosted on 2003-05-19 at 21:12:20ID: 8548331
You cannot send an EOF. An EOF only occurs when the stream is closed.