Thomas,<br><br>Thanks a lot for your help. I feel there is light at the end of the tunnel!!! However, as you can imagine, we have important time constraints. A web client is one of our possibilities (my favorite one) and looks a hard matter. One important point for us, is portability of the client, that is why we considered the web approach. Other options are a lightweight client application written in Python, an applet or a Java Web Start application . To start, we would just implement audio and video transmission, then we could extend the application to support all AG functionalities. I would like to know your opinion about these options.<br>
<br>And finally, would you recommend us to use AGTk 3.0? How feasible is it considering the available resources until now??. Thanks again!!! <br><br>Regards,<br>Luis Galárraga<br><br><div><span class="gmail_quote">2008/2/27, Thomas D. Uram <<a href="mailto:turam@mcs.anl.gov">turam@mcs.anl.gov</a>>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi Luis:<br> <br> I'm the tech lead at Argonne for the Access Grid project. I'm very<br> interested in the work you are proposing, and have some comments:<br> <br> - The API documentation has not, as you've noticed, been updated for<br>
AG3. This needs to be done. I could generate documentation of the web<br> services interfaces fairly easily, which is necessary since there have<br> been some changes from AG2.<br> <br> - There are a couple ways to approach a web-based client. One is to<br>
build an "adapter" between the VenueServer and the web browser; this<br> adapter would accept HTTP from the user, make SOAP calls to the AG<br> VenueServer, and return HTTP responses to the user. I wrote a basic<br>
example of this here: <a href="http://www.accessgrid.org/node/971">http://www.accessgrid.org/node/971</a> . Another,<br> possibly better solution, would be to make the SOAP calls at the client<br> using a JavaScript SOAP implementation. Both of these leave open the<br>
question of how to handle the audio and video.<br> <br> It's a priority for us to update the documentation, but I can't promise<br> when that will be done. If we can help answer questions in the<br> meantime, please don't hesitate to ask either here on the ag-dev list,<br>
or by emailing me directly.<br> <br> Thanks,<br> Tom Uram<br> <br><br> <br> On 2/26/08 3:06 PM, Luis Galárraga wrote:<br> > Greetings:<br> ><br> > I am really interested in Access Grid Development as I take part in a<br>
> small community who is developing a software for videoconferencing<br> > based on AGTk. At the moment, we are in the design phase and some of<br> > us are analyzing the possibility of writing a web client for Venues.<br>
> Of course, there are certain constraints: we only need to use AG in<br> > the easiest configuration, personal node. We would like to know your<br> > opinions about this decision. How difficult and feasible is that?. (We<br>
> have discuss some technical facts and consequences). It is obvious<br> > that the advantages of doing that are numerous.<br> ><br> > Thanks in advance for your contributions to this topic.<br> ><br> > Regards,<br>
> Luis Galárraga<br> </blockquote></div><br>