queue optimization with identical remark

[jcony]

If you have a queue with the same source and destination site, but the items in your queue are going different ways, FlashFXP will disconnect and reconnect. Wouldn't it be more efficient to just retain the connection?

Example:

ARROW, NAME, TARGET, REMARK
<=, File1, /UPLOAD, SITEA TO SITEB
=>, File2, /UPLOAD, SITEA TO SITEB

Will reconnect to both sites inbetween File1 and File2 when FlashFXP is already connected to the required servers.

Just another minor thing that made me go hmmmmm :P

[bigstar]

When you queue an item for transfer the direction of the transfer defines which side is used to perform the transfer.

Typically when you connect to two sites and queue a file from Site A to Site B and then to Site B to Site A the two items in the queue look like this.

ARROW, NAME, TARGET, REMARK
<=, File1, /UPLOAD, SITE A TO SITE B
=>, File2, /UPLOAD, SITE B TO SITE A

From your explanation above it would appear that you are performing two separate steps where Site A is on the left for the first item and then on the right for the second, is this correct?

After the first item is transferred FlashFXP determines if it needs to remain connected to the same sites or connect to a new site. In this case the two sites are swapped so FlashFXP disconnects from Site A and Connects to Site B on the left and then disconnects from Site B and connects to Site A on the right.

You are right this is very inefficient and can be optimized, to do this FlashFXP would need to detect this specific type of condition while processing the item and then swap the item direction flag, the source and target don't change only the direction, in this case it would become

ARROW, NAME, TARGET, REMARK
<=, File1, /UPLOAD, SITE A TO SITE B
<=, File2, /UPLOAD, SITE B TO SITE A

I don't see any immediately issues with implementing this type of change, I will look into implementing this change in the next release.