Bug 2930 – Bug in merging of restart markers

Bug 2930 - Bug in merging of restart markers

Summary:

Bug in merging of restart markers

Status:	RESOLVED FIXED

Product:	RFT
Component:	RFT
Version:	development
Platform:	Macintosh All

Importance:	P3 normal
Target Milestone:	---
Assigned To:	Ravi Madduri

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2005-03-11 14:04 by Ravi Madduri
Modified:	2005-03-11 15:01 (History)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note

You need to log in before you can comment on or make changes to this bug.

Description From Ravi Madduri 2005-03-11 14:04:37

Needs to be fixed

------- Comment #1 From Ravi Madduri 2005-03-11 14:53:11 -------

Restart markers from new server do not include all the transfer state as was
the case before. Only 
updates of restart markers are sent instead of whole state. so for example if
iam transferring a 6GB file 
after second restart i would get a restart marker from server which would be
like 234343-312133. So 
when i use this when i restarted the file from 0-234343 would be transferred
again. So when i store the 
marker in the database it should always be from 0-<last marker i get> so when i
restart I send REST 0-
<marker>.

------- Comment #2 From Ravi Madduri 2005-03-11 15:01:41 -------

Fixed in CVS