Difference: ApplicationsMessagingInitialQuestionsTwo (1 vs. 3)

Revision 32012-06-26 - root

 
META TOPICPARENT name="ApplicationsMessagingInitialQuestions"


Which set of platforms/languages should be able to access the messaging system?


Fortran and other legacy codes might easily be able to create a message with a given syntax regardless of the transport method used. One use case to consider is that of an existing F77 theory code that might easily be modified to display table/image results using this system. --Mike


Platforms: Windows XP, Mac OSX, Linux. That is, all the desktop platforms in common use. This might seem obvious, but it eliminates some Unix-only solutions.

Languages/environments: for clients, at least C#, C, C++, Java, Perl, Python, TCL, IDL. Fortran would be nice. (Of course, with a wire protocol like XMLRPC, we'll get many other languages "for free").

-- JohnTaylor - 08 Feb 2007

Revision 22007-02-08 - JohnTaylor

 
META TOPICPARENT name="ApplicationsMessagingInitialQuestions"

Deleted:
<
<
 
<--  
-->

Which set of platforms/languages should be able to access the messaging system?


Fortran and other legacy codes might easily be able to create a message with a given syntax regardless of the transport method used. One use case to consider is that of an existing F77 theory code that might easily be modified to display table/image results using this system. --Mike
Added:
>
>

Platforms: Windows XP, Mac OSX, Linux. That is, all the desktop platforms in common use. This might seem obvious, but it eliminates some Unix-only solutions.

Languages/environments: for clients, at least C#, C, C++, Java, Perl, Python, TCL, IDL. Fortran would be nice. (Of course, with a wire protocol like XMLRPC, we'll get many other languages "for free").

-- JohnTaylor - 08 Feb 2007

 

Revision 12007-02-08 - JohnTaylor

 
META TOPICPARENT name="ApplicationsMessagingInitialQuestions"


<--  
-->

Which set of platforms/languages should be able to access the messaging system?


Fortran and other legacy codes might easily be able to create a message with a given syntax regardless of the transport method used. One use case to consider is that of an existing F77 theory code that might easily be modified to display table/image results using this system. --Mike
 
This site is powered by the TWiki collaboration platform Powered by Perl This site is powered by the TWiki collaboration platformCopyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback