Skip to Content.
Sympa Menu

perfsonar-dev - Re: [Fwd: [pS-dev] perfsonar: r2323 - in trunk/perfsonar/src/org/perfsonar: commons/messages service/commons/engine]

Subject: perfsonar development work

List archive

Re: [Fwd: [pS-dev] perfsonar: r2323 - in trunk/perfsonar/src/org/perfsonar: commons/messages service/commons/engine]


Chronological Thread 
  • From: Roman Łapacz <>
  • To: "Jeff W. Boote" <>
  • Cc: Roman Lapacz <>, Jason Zurawski <>, Maciej Glowiak <>, "" <>
  • Subject: Re: [Fwd: [pS-dev] perfsonar: r2323 - in trunk/perfsonar/src/org/perfsonar: commons/messages service/commons/engine]
  • Date: Sat, 14 Apr 2007 11:44:09 +0200

Jeff W. Boote napisał(a):
This message handler is a part of pS base so all it's needed to have it working is adding its name (LookupInfoRequest) to service.properties file in service.ma.message_types property.

Is there some reason not to use the LSQuery message type? It is already well defined for the LS. If you can reuse it, then clients can reuse most of the same code they use to query an LS for multiple services to query the single service.

I think we should strive to reduce the number of distinct message types that are in use... (If there is a reason not to use it - I'm not against creating new needed message types. I would just like to see re-use whenever possible.)

I thought I would reuse existing message handler (LSQueryRequest) but unfortunately I could not. The implementation did not allow for that. I had to create new one and introduce new type of message.

Roman




Archive powered by MHonArc 2.6.16.

Top of Page