Dear All,
Hello. Here I want to ask a question which is nothing to do with the detail of
grid technology, but a design pattern related to grid portal development.
I have established a computational grid infrastracture in my lab using GT and
relavant technology, and now I want to develop a portal prototype. I plan to
use a machine to serve as the portal server, and end users access the grid
resources through the client tool, which use the services provided by the
portal server. Currently I do not plan to develop the Web-based Portal due to
the time limitation(I am more familiar with desktop GUI developing).
Obviously there are some issues must be addressed in the portal server, such as
certificates, job submission, access the web mds... Well, here is my question:
Should I encapsulate those functions as several web servers which can be
deployed in the GT container (such as SingleJobSubmissionService,
ArrayJobSubmissionService, ComputeResourcesListService...) and let the client
tool access those web services directly, or should I write a daemon on the
portal server, which listens the requests of the clients and then access the
grid infrastructure, and finally send the response to the client, just as the
classical C-S model.
So, I want to disscuss it with you. Any suggestion will be much appraciated.
Thanks!
Tracy
