Very interesting. I look forward to learning more about it when it becomes
available. What
is the middleware? Perl, Java, other? What is the crossplatform foundation for
the client?
The split-server configuration is similar to the way that we configure VMACS in
production
systems except that
Medsphere has certainly put money into the development
of this technology. And I will understand if they
want a return on that investment.
Is there any way that we could develop equivalent
technology in an opensource fashion?
I don't understand the arrangement he described.
Kevin
--- Jim
-4505
Tel:315.330.2422
Fax:315.330.7009
Email: [EMAIL PROTECTED]
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Kevin
Toppenberg
Sent: Thursday, July 21, 2005 2:57 PM
To: hardhats-members@lists.sourceforge.net
Subject: RE: [Hardhats-members] CPRS HTTPS
I don't think you're wrong. M2Web is a kind of M based application
server. JBoss and Tomcat are open source options for Java based
application servers (and both come installed on OS X out of the box,
BTW). I don't know that much about M2Web, but from everything I've
heard on this list, it's
On Thu, 2005-07-21 at 15:45 -0400, Joseph Dal Molin wrote:
Sounds like M2Web...but I may be wrongit uses Apache..
J.
The difference is that our middle-ware publishes a SOAP API that can be
used by any SOAP aware client (And basically every language out there
has a SOAP library of
...is it correct to infer from this and your earlier post that you have
rewritten CPRS?
J.
Todd Berman wrote:
On Thu, 2005-07-21 at 15:45 -0400, Joseph Dal Molin wrote:
Sounds like M2Web...but I may be wrongit uses Apache..
J.
The difference is that our middle-ware publishes a
Right, and in principle, an M server could be made to speak SOAP if
there were interesdt in doing so. An alternative would be to use a more
conventional application server and something like VistaLink for data
access. This may be preferable, given that M platforms aren't
particularly well suited
Kevin wrote:
Medsphere has certainly put money into the development
of this technology. And I will understand if they
want a return on that investment.
I am sure that they will see a tremendous return if their solution is widely
adopted
whether Open Source or not. Making it Open Source would
On Thu, 2005-07-21 at 16:31 -0400, Joseph Dal Molin wrote:
...is it correct to infer from this and your earlier post that you have
rewritten CPRS?
J.
Yes, it would be correct to infer that we have a crossplatform client
that provides the same feature-set as CPRS.
--Todd
M2Web provides a MUMPS based framework and tools for developing and running web
applications and serving MUMPS data on the web in various formats including
HTML, JSON
(Javascript Object Notation), and XML. We (UC Davis VMTH) haven't yet used the
XML format
very much because the JSON format has
On Thu, 2005-07-21 at 16:31 -0400, Joseph Dal Molin wrote:
...is it correct to infer from this and your earlier post that you have
rewritten CPRS?
J.
Yes, it would be correct to infer that we have a crossplatform client
that provides the same feature-set as CPRS.
--Todd
Todd,
On Thu, 2005-07-21 at 16:25 -0500, [EMAIL PROTECTED] wrote:
On Thu, 2005-07-21 at 16:31 -0400, Joseph Dal Molin wrote:
...is it correct to infer from this and your earlier post that you have
rewritten CPRS?
J.
Yes, it would be correct to infer that we have a crossplatform
TCP/IP handling is a total non-issue with M2Web. Most applications find their
input in
local variables (most generically htInput(name) ) and either simply write their
response
to their home device or (even simpler) set it in the local variable htReturn.
M2web currently uses a CGI interface from
No, I've written applications using both the SAX and DOM interfaces of
the MXML parser. I actually rather like it. But there are limitations,
such as being restricted to 7-bit ASCII and problems with TCP/IP
streams. My application have always read and written host files, and
I've found that it has
I wonder, has anyone given serious thought to having a CPRS client connect to
the RPC
broker via HTTPS (HTTP + SSL)? That would seem to me to be the ideal solution
for
connecting internet accessible services.
I was thinking that it might not be at all difficult to provide the RPC
interface via
On Wed, 2005-07-20 at 14:22 -0700, Jim Self wrote:
I wonder, has anyone given serious thought to having a CPRS client connect to
the RPC
broker via HTTPS (HTTP + SSL)? That would seem to me to be the ideal solution
for
connecting internet accessible services.
That is basically (well, a
This sort of approach would undoubtedly simplify many things. Since SSL is
*THE* secure
protocol for virtually all secure web services, I imagine that it was simply
overlooked
not rejected.
Could you give us more specifics as to what you (medsphere) are doing and is it
available
as Open
17 matches
Mail list logo
