Home » Archived » Riena » How to use IRemoteProgressMonitorRegistry?
| | | |
| Re: How to use IRemoteProgressMonitorRegistry? [message #27015 is a reply to message #26975] |
Fri, 19 June 2009 07:19   |
 Ralf Heilek
Messages: 12
Registered: July 2009 |
Junior Member |
|
|
Christian Campo schrieb:
> Ralf Heilek schrieb:
>> Christian Campo schrieb:
>>> Ralf Heilek schrieb:
>>>> Hi,
>>>>
>>>> I build an client/server application on top of the riena platform
>>>> and want to monitor a long running server operation on the client.
>>>>
>>>> In org.eclipse.riena.example.client i found an example using
>>>> IRemoteProgressMonitorRegistry (service) to monitor another service.
>>>> Unfortunately, the example is only a client application and fakes
>>>> the remote service call.
>>>>
>>>> I guess that the server provides the RemoteProgressMonitorRegistry
>>>> and the client registers a proxy to add a ProgressMonitor before
>>>> calling a remote service.
>>>>
>>>> A the moment the client and server project depend on
>>>> org.eclipse.riena.communication.core and get their own
>>>> RemoteProgressMonitorRegistry by the Activator of this bundle.
>>>>
>>>> Can i use this implementation in a real client/server environment?
>>>>
>>>> Thanks, Ralf
>>> Hi Ralf,
>>>
>>> everything is on the client. The server does not even know about the
>>> progress monitor. Currently we only monitor the progress on the
>>> communication line. So if you server takes 60 seconds to process a
>>> request and there is no action on the line during that time, there is
>>> no chance to monitor that. So its more meant for calls where the
>>> parameter or the return value is either large or you are using a very
>>> weak and thin connection with little speed. Then you get events for
>>> every 512 bytes that are sent or received.
>>>
>>> The RemoteProgressMonitorITest class (in o.e.riena.tests) shows you
>>> how to use that with a real running remote service call.
>>>
>>> The fake implementation is used where we show how that
>>> ProgressMonitor Events can be visualized in an Eclipse Job.
>>>
>>> Does that information help ?
>>>
>>> if not let me know
>>>
>>> christian campo
>>
>> Hi Christian,
>>
>> the hint to riena.tests helped me understand the
>> RemoteProgressMonitorRegistry.
>>
>> Are you planning something like that in further releases?
>>
>> Thanks, Ralf
> Are we planning something like WHAT in further releases ?
>
> christian campo
Sorry,
I meant to monitor a long running server operation at the client. At the
moment there is no chance to show the current state of a server operation.
In my application i processing a huge data object to a database and it
would be nice to show the current state of the process at the client. So
i need something like a simple asynchronous callback to the client.
Thanks, Ralf
|
|
|
| Re: How to use IRemoteProgressMonitorRegistry? [message #27055 is a reply to message #27015] |
Fri, 19 June 2009 08:37 |
Christian Campo
Messages: 596
Registered: July 2009 |
Senior Member |
|
|
Ralf Heilek schrieb:
> Christian Campo schrieb:
>> Ralf Heilek schrieb:
>>> Christian Campo schrieb:
>>>> Ralf Heilek schrieb:
>>>>> Hi,
>>>>>
>>>>> I build an client/server application on top of the riena platform
>>>>> and want to monitor a long running server operation on the client.
>>>>>
>>>>> In org.eclipse.riena.example.client i found an example using
>>>>> IRemoteProgressMonitorRegistry (service) to monitor another
>>>>> service. Unfortunately, the example is only a client application
>>>>> and fakes the remote service call.
>>>>>
>>>>> I guess that the server provides the RemoteProgressMonitorRegistry
>>>>> and the client registers a proxy to add a ProgressMonitor before
>>>>> calling a remote service.
>>>>>
>>>>> A the moment the client and server project depend on
>>>>> org.eclipse.riena.communication.core and get their own
>>>>> RemoteProgressMonitorRegistry by the Activator of this bundle.
>>>>>
>>>>> Can i use this implementation in a real client/server environment?
>>>>>
>>>>> Thanks, Ralf
>>>> Hi Ralf,
>>>>
>>>> everything is on the client. The server does not even know about the
>>>> progress monitor. Currently we only monitor the progress on the
>>>> communication line. So if you server takes 60 seconds to process a
>>>> request and there is no action on the line during that time, there
>>>> is no chance to monitor that. So its more meant for calls where the
>>>> parameter or the return value is either large or you are using a
>>>> very weak and thin connection with little speed. Then you get events
>>>> for every 512 bytes that are sent or received.
>>>>
>>>> The RemoteProgressMonitorITest class (in o.e.riena.tests) shows you
>>>> how to use that with a real running remote service call.
>>>>
>>>> The fake implementation is used where we show how that
>>>> ProgressMonitor Events can be visualized in an Eclipse Job.
>>>>
>>>> Does that information help ?
>>>>
>>>> if not let me know
>>>>
>>>> christian campo
>>>
>>> Hi Christian,
>>>
>>> the hint to riena.tests helped me understand the
>>> RemoteProgressMonitorRegistry.
>>>
>>> Are you planning something like that in further releases?
>>>
>>> Thanks, Ralf
>> Are we planning something like WHAT in further releases ?
>>
>> christian campo
>
> Sorry,
>
> I meant to monitor a long running server operation at the client. At the
> moment there is no chance to show the current state of a server operation.
>
> In my application i processing a huge data object to a database and it
> would be nice to show the current state of the process at the client. So
> i need something like a simple asynchronous callback to the client.
>
> Thanks, Ralf
Hi Ralf,
actually I was think about doing that once. Rather than doing using async callbacks, I would do something like "server
ticks". So the call from client to server is open with the request and the server is able to report on that open line
with status updates on what is happening on the server. I never that this was so complicated to implement that on top of
Hessian. But still it has to be done and doing is some sort of commitment to this API. So that is why we havnt done that
yet.
As with any other topic. Things dont get done if they are discussedd here on the newsgroup but only if they materialize
into bugzilla enhancement requests. So if you think that is important. Add a bug entry to track it.
christian campo
|
|
| | | |
| Re: How to use IRemoteProgressMonitorRegistry? [message #582845 is a reply to message #26975] |
Fri, 19 June 2009 07:19 |
Ralf Heilek
Messages: 12
Registered: July 2009 |
Junior Member |
|
|
Christian Campo schrieb:
> Ralf Heilek schrieb:
>> Christian Campo schrieb:
>>> Ralf Heilek schrieb:
>>>> Hi,
>>>>
>>>> I build an client/server application on top of the riena platform
>>>> and want to monitor a long running server operation on the client.
>>>>
>>>> In org.eclipse.riena.example.client i found an example using
>>>> IRemoteProgressMonitorRegistry (service) to monitor another service.
>>>> Unfortunately, the example is only a client application and fakes
>>>> the remote service call.
>>>>
>>>> I guess that the server provides the RemoteProgressMonitorRegistry
>>>> and the client registers a proxy to add a ProgressMonitor before
>>>> calling a remote service.
>>>>
>>>> A the moment the client and server project depend on
>>>> org.eclipse.riena.communication.core and get their own
>>>> RemoteProgressMonitorRegistry by the Activator of this bundle.
>>>>
>>>> Can i use this implementation in a real client/server environment?
>>>>
>>>> Thanks, Ralf
>>> Hi Ralf,
>>>
>>> everything is on the client. The server does not even know about the
>>> progress monitor. Currently we only monitor the progress on the
>>> communication line. So if you server takes 60 seconds to process a
>>> request and there is no action on the line during that time, there is
>>> no chance to monitor that. So its more meant for calls where the
>>> parameter or the return value is either large or you are using a very
>>> weak and thin connection with little speed. Then you get events for
>>> every 512 bytes that are sent or received.
>>>
>>> The RemoteProgressMonitorITest class (in o.e.riena.tests) shows you
>>> how to use that with a real running remote service call.
>>>
>>> The fake implementation is used where we show how that
>>> ProgressMonitor Events can be visualized in an Eclipse Job.
>>>
>>> Does that information help ?
>>>
>>> if not let me know
>>>
>>> christian campo
>>
>> Hi Christian,
>>
>> the hint to riena.tests helped me understand the
>> RemoteProgressMonitorRegistry.
>>
>> Are you planning something like that in further releases?
>>
>> Thanks, Ralf
> Are we planning something like WHAT in further releases ?
>
> christian campo
Sorry,
I meant to monitor a long running server operation at the client. At the
moment there is no chance to show the current state of a server operation.
In my application i processing a huge data object to a database and it
would be nice to show the current state of the process at the client. So
i need something like a simple asynchronous callback to the client.
Thanks, Ralf
|
|
|
| Re: How to use IRemoteProgressMonitorRegistry? [message #582857 is a reply to message #27015] |
Fri, 19 June 2009 08:37 |
Christian Campo
Messages: 596
Registered: July 2009 |
Senior Member |
|
|
Ralf Heilek schrieb:
> Christian Campo schrieb:
>> Ralf Heilek schrieb:
>>> Christian Campo schrieb:
>>>> Ralf Heilek schrieb:
>>>>> Hi,
>>>>>
>>>>> I build an client/server application on top of the riena platform
>>>>> and want to monitor a long running server operation on the client.
>>>>>
>>>>> In org.eclipse.riena.example.client i found an example using
>>>>> IRemoteProgressMonitorRegistry (service) to monitor another
>>>>> service. Unfortunately, the example is only a client application
>>>>> and fakes the remote service call.
>>>>>
>>>>> I guess that the server provides the RemoteProgressMonitorRegistry
>>>>> and the client registers a proxy to add a ProgressMonitor before
>>>>> calling a remote service.
>>>>>
>>>>> A the moment the client and server project depend on
>>>>> org.eclipse.riena.communication.core and get their own
>>>>> RemoteProgressMonitorRegistry by the Activator of this bundle.
>>>>>
>>>>> Can i use this implementation in a real client/server environment?
>>>>>
>>>>> Thanks, Ralf
>>>> Hi Ralf,
>>>>
>>>> everything is on the client. The server does not even know about the
>>>> progress monitor. Currently we only monitor the progress on the
>>>> communication line. So if you server takes 60 seconds to process a
>>>> request and there is no action on the line during that time, there
>>>> is no chance to monitor that. So its more meant for calls where the
>>>> parameter or the return value is either large or you are using a
>>>> very weak and thin connection with little speed. Then you get events
>>>> for every 512 bytes that are sent or received.
>>>>
>>>> The RemoteProgressMonitorITest class (in o.e.riena.tests) shows you
>>>> how to use that with a real running remote service call.
>>>>
>>>> The fake implementation is used where we show how that
>>>> ProgressMonitor Events can be visualized in an Eclipse Job.
>>>>
>>>> Does that information help ?
>>>>
>>>> if not let me know
>>>>
>>>> christian campo
>>>
>>> Hi Christian,
>>>
>>> the hint to riena.tests helped me understand the
>>> RemoteProgressMonitorRegistry.
>>>
>>> Are you planning something like that in further releases?
>>>
>>> Thanks, Ralf
>> Are we planning something like WHAT in further releases ?
>>
>> christian campo
>
> Sorry,
>
> I meant to monitor a long running server operation at the client. At the
> moment there is no chance to show the current state of a server operation.
>
> In my application i processing a huge data object to a database and it
> would be nice to show the current state of the process at the client. So
> i need something like a simple asynchronous callback to the client.
>
> Thanks, Ralf
Hi Ralf,
actually I was think about doing that once. Rather than doing using async callbacks, I would do something like "server
ticks". So the call from client to server is open with the request and the server is able to report on that open line
with status updates on what is happening on the server. I never that this was so complicated to implement that on top of
Hessian. But still it has to be done and doing is some sort of commitment to this API. So that is why we havnt done that
yet.
As with any other topic. Things dont get done if they are discussedd here on the newsgroup but only if they materialize
into bugzilla enhancement requests. So if you think that is important. Add a bug entry to track it.
christian campo
|
|
|
Goto Forum:
Current Time: Wed Jan 15 07:11:48 GMT 2025
Powered by FUDForum. Page generated in 0.04726 seconds |
] 
Search
Help
Register
Login
Home
