In fact we aim for integrating VR-collaboration into AccessGrid. At the moment I am evaluating the different methods for integration. We already did a small shared application coupling the UI part of the VR-controll software with AccessGrid. Adiditionally I am working on a method of allowing our render software to have a connection to access grid. As I said this just experimental at the moment. But I think it might be a good idea to consider our VR-rendering software as a kind of a capability of a node, or in more detail have some kind of daemon or server which provides a interface to the VR environment for other access grid participants. This server would then also only be started if you enter a venue or leave it, providing a continues stream of 3D data. Initially I first want to check out the complexity of integration of our application as a service before I decide on one way of implementation. Therefore I wrote a small client server app just sending information using sockets. I now want to incorporate this app into a producer service python script so there is alaways a server app running on the node and of course get a client instance of the app running when entering a venu on the server. But as described I still struggle with invoking my server app. Furthermore I don' t know at which point to integrate the client side application call.
Thanks Michael Ivan R. Judson wrote: >Hi Michael, > >I'm sorry I haven't replied to your email yet, can you tell me what the >application you are trying to incorporate does? It might be better >integrated as a shared application rather than a node service, the >difference being that shared applications are what users interact with, like >a shared editor or shared rasmol application, whereas a node service is >providing some underlying capability, like shared video or shared audio. >Once configured the users doesn't start and stop the node services >typically, there are automatically started and stopped when they enter a >venue. > >I hope that helps a bit, please let me know what I can do to help. > >--Ivan > > > >>-----Original Message----- >>From: [email protected] >>[mailto:[email protected]] On Behalf Of Michael Braitmaier >>Sent: Thursday, May 06, 2004 5:09 AM >>To: [email protected] >>Subject: [AG-TECH] Struggling with starting of producer >>service and encapsulated executable >> >>Currently I am trying to incorporate a simple executeable >>into my VideoProducerService-derived own ProducerService., >>but I can't figure out some aspects of how the producer service works. >>Especially I am stuck with the start method of the service. >>As far as I understand it, for example the Videoproducer >>service does nothing more than calling vis with appropriate >>parameters passed in the options array. Therefore I wanted to >>replace vic by my own executeable and accordingly change the >>options passed to the called AGService._Start method. But >>when I remove the options >>self.streamDescription.location.host and >>self.streamDescription.location.port my producer service >>can't be added to my service manager because the service >>manager reports that the service is unreachable. I thought >>these values are only needed for vic to be able to broadcast >>its video stream and receive video streams, so I should be >>able to pass my own server information format at this point >>which is understandable by my executeable. So what do I have >>to pay attention to when replacing vic with my own >>executeable concerning the start method of the producer >>service, to avoid my service being unreachable ? >> >>Any help would be greatly appreciated. >>Michael >> >>-- >>Michael Braitmaier >>HLRS >>University of Stuttgart >>Germany >> >> >> >> >> > > > > -- Michael Braitmaier HLRS University of Stuttgart Germany
