Member Avatar for CuteOrchidd

Hi all,
I want to know the java code for transfering the multiple files between server nodes to server node.
With advance thanks,
CuteOrchid

  • 4 Contributors
  • 4 Replies
  • 265 Views
  • 1 Week Discussion Span
  • Latest Post Latest Post by CuteOrchidd

Dani AI

Generated

Decide the transfer model first (push vs pull, single archive vs many files, atomic vs streaming) and pick an established protocol that matches that model rather than building a raw-socket solution from scratch. Established choices (SFTP/SCP, rsync over SSH, HTTPS with ranged requests, or an existing file-sync tool) handle authentication, resume, and integrity for free; a custom protocol is only worth the effort for special constraints (very high throughput, custom metadata, or embedded environments).

For a Java service, prefer a well-tested client/server library instead of reinventing I/O. Libraries and APIs to consider: an SSH/SFTP client library for secure transfers, a high-level VFS library for unified file operations, and java.nio (FileChannel/zero-copy) for efficient local streaming when performance matters. Ensure transfers support resume/seek for large files and use checksums (SHA-256) in a manifest so receivers can verify integrity before promoting files to production locations.

A practical workflow that fits most use cases:

  • Produce a manifest listing paths, sizes, timestamps and checksums (one line per file).
  • Optionally pack and compress small files into a single archive to reduce overhead for many small files.
  • Transfer into a temp directory on the target, verify checksums against the manifest, then atomically move validated items into the final directory.
  • Implement retries with exponential backoff, limit parallel transfers to avoid saturating disk or network, and log progress with per-file status for easy recovery.

Operational cautions: use key-based authentication and TLS/SSH to protect data, open only required ports and test across real network conditions (latency, NAT, firewalls). Preserve permissions/timestamps if needed, and run scale tests to tune thread pools and chunk sizes. This advice builds on points made earlier in the thread (low-level I/O and protocol choice) and points toward using existing, proven tools for robust production transfers.

Recommended Answers

All 4 Replies

Member Avatar for masijade

We will NOT write code for you. To actually help you we will need more information though. Here some info to get you started

FileInputStream
FileOutputStream
Socket
ServerSocket

Member Avatar for jwenting

you'll need to know what protocol to use, and then find or write a library implementing that protocol.

good luck, and as said we're not going to do it for you.

Member Avatar for CuteOrchidd

Thank a lot for all suggestion and help.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.