[
http://jira.codehaus.org/browse/XFIRE-966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomasz Sztelak closed XFIRE-966.
--------------------------------
Assignee: Tomasz Sztelak (was: Dan Diephouse)
Resolution: Won't Fix
> Seeking a mechanism for I/O progress monitoring
> ------------------------------------------------
>
> Key: XFIRE-966
> URL: http://jira.codehaus.org/browse/XFIRE-966
> Project: XFire
> Issue Type: Wish
> Affects Versions: 1.2.5
> Environment: MacOSX/Windows XP/Fedora Core w/JDK 1.6
> Reporter: Sean Doyle
> Assignee: Tomasz Sztelak
> Priority: Minor
>
> Hi..
> I'm using XFire for transfer of fairly large (20+MB) images using MTOM.
> Everything works pretty well. However - if the bandwidth is limited these
> transfers can take some time and I'd like to show in my client some
> indication of progress (bytes transferred/% completed..). I'd like to add
> some type of callback or I/O filter mechanism which basically passed all the
> data through but updated the byte counts. I can't do this on the attachment
> boundaries - the attachments are too big for the frequency of feedback I
> want to give my users.
> I can think of two approaches - I'm not sure that I like either one.
> 1. I could extend (for the upload case) FileDataSource and have my own
> I/O streams that kept track of the byte count.
> 2. I could add input/output handlers to an instance of
> org.codehaus.xfire.client.Client.
> The only problem with #1 is that it requires a few classes; #2 I'm not
> completely sure how to do (I think I'd look at the LoggingHandler as a
> model).
> Is there a better way to do this? I don't need extremely fine granularity -
> if it updated every hundred K or so that would be adequate for what I need.
> Thanks.
> Sean
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
