SOAPing without a Web Server

• Download source code- 43.9 Kb
• Download built binaries- 356 Kb

ATL Server is a new set of classes in ATL for creating Web Applications and Web Services. These Web Services are completely compatible with clients written in C++, C#, VB and other tools that can call a Web Service through SOAP. The Web Service support in ATL Server only supports invocation over an HTTP tranport for this version, however like the rest of ATL, ATL Server is designed to be very flexible. You may wish to create Web Services which can be called over other transport mechanisms, such as TCP/IP, and this article will help explain how you would go about changing the default transport ATL Server supports for Web Services. Two examples are included, one implementing a Web Service which can be called over TCP/IP and another sample which uses a Floppy Disk for the transport

This article shows how to separate the SOAP support offered by ATL Server from the ISAPI framework, allowing use of ATL Server to build SOAP servers and clients over virtually any communication channel.

Summary:

• Server Side
• Client Side
• Transport Channels
• An Extension: HTTPListenerTransport
• Final Considerations

Server Side

The ATL Server Web Service Wizard will generate the code for a Web Service exposed through HTTP. The Web Service is implemented as a class with the following declaration:

[
request_handler(name="Default", sdl="GenSimpleSoapAppServiceSDL"),
soap_handler(
		name="SimpleSoapAppService", 
		namespace="urn:SimpleSoapAppService",
		protocol="soap"
	)
]
class CSimpleSoapAppService :
	public ISimpleSoapAppService

In this code sequence, the attributes before the class declaration do most of the exposing. The soap_handler attribute will inject the following methods : DispatchSoapCall, ParseSoapHeaders and __AtlGetSDL. These methods are required for required for handling SOAP messages and mapping them to internal method calls and also for wrapping the result of internal methods invocations to SOAP responses. (The MSDN library coming with Visual Studio.NET 7.0 Beta1 contains details on the code injected by this attribute). The request_handler attribute will make it able to handle HTTP requests. If the transport layer is not going to be HTTP, the request_handler attribute is no longer needed, so it can be commented out.

The CSoapHandler<> class in atlsoap.h is designed to handle SOAP requests through HTTP. The entry point for handling an HTTP SOAP request is:

HTTP_CODE HandleRequest(AtlServerRequest *, IServiceProvider *)

The request body and the SOAP related HTTP header ("SOAPAction") are retrieved from the ISAPI extension through the pServerRequest(an ECB wrapper)member of the AtlServerRequest* parameter. The pServerRequest object provides methods from reading the request body, reading the SOAPAction HTTP header and writing the SOAP response back to the client. As the purpose is to replace the HTTP transport, we need to find another way to launch the SOAP request processing and to provide it with a way of performing the same operations.

This is solved by creating a CSoapHandler derivative, CSoapTransportHandler, that implements the following entry point (file SoapTransportSrv.h of the downloadable code):

HTTP_CODE InvokeSoapMethod(stSoapTransportDescription	*pTransInfo) 

And the stSoapTransportDescription structure is defined as:

struct  stSoapTransportDescription
{
// the stream to write the SOAP response to

	IWriteStream     *pWriteStream;	
// the stream to read the SOAP request from

	IStream	         *pReadStream;
// the SOAP Action	

	CStringA          strSOAPAction;	 
// the service provider

	IServiceProvider *pServiceProvider; 
};

Perhaps the only member that needs a few details is pServiceProvider. It allows the SOAP servers to share services exactly as those in an ISAPI dll. It can be NULL in an implementation, as long as the SOAP servers will not attempt to use it.

Now, the SOAP server class generated by the wizard has to be modified to use the new CSoapTransportHandler functionality. The new code would look like:

[
	//request_handler(name="Default", sdl= "GenSimpleSoapAppWSDL"),

	soap_handler(
		name="SimpleSoapAppService", 
		namespace="urn:SimpleSoapAppService",
		protocol="soap"
	)
]
class CSimpleSoapAppService :
	public CSoapTransportHandler<CSimpleSoapAppService>,
	public ISimpleSoapAppService
	...

There is no other modification that has to be done in the wizard-generated server code.

Right now, the SOAP server can be instantiated and the SOAP methods can be invoked through CSoapTransportHandler::InvokeSoapMethod, therefore with custom streams to read from and write to, and it does not depend on the ATL Server HTTP support anymore.

The instantiation of the server(s) is handled by another class, CSoapDispatcher, implemented in the soapDispatch.h file. The CSoapDispatcher class fills a stSoapTransportDescription structure, then instantiates a SOAP server and invokes a SOAP call like below

	stSoapTransportDescription transInfo;
	// set the transInfo stream pointers

	...
	CComObjectNoLock<CSimpleSoapAppService> srv;
	HRESULT	hRet = S_OK;
	try
	{
		hRet = srv.InvokeSoapMethod( &transInfo );
	}
	catch(...)
...

At this point, a server application only has to:

• get the SOAP request and the SOAP Action header through any transport channel
• wrap the request in an IStream interface
• provide an IWriteStream to store the response
• invoke CSoapDispatcher::DispatchCall
• send the content of the write stream (the SOAP response) over any transport channel to the client

Client Side

The SOAP proxy class generated by sproxy.exe has the following prototype:

class CSimpleSoapAppService : public CSoapSocketClient
...

By inspecting the code generated by sproxy.exe, one can notice that only a few methods/members of the CSoapSocketClient are actually used by the proxy class. These would be

• the constructor
• HRESULT SendRequest(LPCTSTR tszAction) throw()
• void Cleanup() throw()
• m_Stream, used as an IStream interface to store the request before sending
• m_ReadStream, used as an IStream interface to store the response before parsing

The method that does most of the work here is SendRequest. This method is supposed to send the request from m_Stream to the SOAP server and to fill m_ReadStream with the server response. By replacing (in the sproxy.exe generated file) CSoapSocketClient with a custom class that contains all these methods and attributes, the actual channel used to send the request to the SOAP server only depends on the implementation of the SendRequest method.

It is exactly what happens in the attached sample code. To reuse the sproxy.exe generated code for such different transport classes, the following modification would be useful:

template<TTransportClass>
class CSimpleSoapAppService : public TTransportClass
...

Transport Channels

The sample implements the following transport channels:

• Communication through files saved on a storage media(in the FloppyTransport folder)
• TCP/IP communication (in the TCPIPTransport folder)

Each transport channel implementation contains a client application and a server application. The server uses the SOAP server included in the Include folder (which is built as described above). The code in the server application only takes care of the transport. The client application only implements the transport specific class to act as a TTransportClass parameter for the modified class generated by sproxy.exe

Please note that the modifications specified above only allow sending/receiving SOAP messages over the custom channel. They do not allow retrieving the description (SDL) for the service. Therefore, a limitation of the TCPIPTransport and FloppyTransport samples is that the SDL used in generating the proxy has to be generated outside of the sample. The one used in the applications specified above is saved as simpleSoapSrv.wsdl in the Include folder. To get the server description, one would have to create the SOAP server through the wizard, complete the interface, then save the SDL through the default HTTP way provided by ATL Server.

An Extension : HTTPListenerTransport

This folder contains an enhanced version of the TCPIPTransport server. This server listens on a specified TCPIP port, but it accepts HTTP requests. It provides a way of responding to .disco requests, to generate the SDL for the implemented SOAP servers and also to accept SOAP invocations. This server can provide a very light-weight, complete, SOAP implementation, without requiring an HTTP server to be installed on the machine. To create a client for this light server, just use the Add Web Reference wizard from the Visual Studio.NET 7.0 Beta1 IDE, and point the wizard to the following URL:

http://<your_machine>:<ListenPort>/disco

If you build the HTTPListenerServer sample, the URL would become:

http://localhost:333/disco

The C# client provided for this server (HttpListenerCSharpClient) is generated this way

Final Considerations

To build the sample code, just unzip the source archive, then load and build the solution file (ATLSSoapTransport.sln)

An updated version of the sample code will be included as an ATL Server sample starting with Visual Studio.NET Beta2. It will add the following :

• Compliance with the latest SOAP specification
• Compliance with the latest WSDL ( service description language) specification
• Microsoft Message Queuing transport

You must Sign In to use this message board.

FAQ    Noise Tolerance Very HighHighMediumLowVery Low   Layout Expand Posts & RepliesThread ViewNo JavascriptNo JS + Preview   Per page 102550

Msgs 1 to 25 of 44 (Total in Forum: 44) (Refresh) FirstPrevNext

BeginParse( ) fails after VS2005 installation m.delara 21:28 8 Aug '06   Thank you very much for this article. This has been very helpful to me in implementing the simple SOAP server needed for my requirements. I have recently encountered a problem which I hope somebody has an idea on. I applied what I learned and made a simple SOAP server as part of a much larger module using VS2003 in Win2K. This has been working well for the past few months. However, when I recently installed VS2005, BeginParse( ) would now always return Invalid Soap Request error. There has been no changes in the code as well as in the client request. Testing it on a different PC with no VS2005 installation resulted in normal S_OK. Is there some adjustment I should do for VS2005? Thanks in advance. Sign In·View Thread·PermaLink Re: BeginParse( ) fails after VS2005 installation Wang JunGe 23:20 14 Nov '06   Hi, I have figure out what cause the problem through some debuging, it is because the MSXML version. 1. The worked one use MSXML3 SP5, the problem one use MSXML3 SP7. Because the OS can't revert back to MSXML3 SP5, so I just simply overwirte the MSXML3.DLL (SP7) with MSXML3.dll(SP5) in safe mode, then everything is working smoothly. I guess that the MSXML3 SP7 may be have different checking conditon for XML format, so it parses the XML failed, and MSXML3 SP5 parses it success. Sign In·View Thread·PermaLink 1.33/5 (2 votes) Reading Responce from Web using unmanaged c++ client LillyPrashanthi 3:24 26 Sep '05   Having edited the TCPClient on msdn Soap Transport Samples, to send a request to some webserver say "Hello.asmx", Looks could send the request successfully but unable to read the response from the web i.e "Error reading from the socket". Looking forward for help from experts to resolve. Here copying the src for wht exactly I am trying to do. ***************************************************** Web Service: Hello.asmx ----------------------------------------------------- <%@ WebService Language="C#" Class="sample" %> using System.Web.Services; [WebService(Namespace="urn:sample")] public class sample { [ WebMethod ] public string Hello(string name) { return "Hello " + name; } } *************************************************** Unmanged C++ Client: SoapClient.cpp --------------------------------------------------------- // SoapClient.cpp : Defines the entry point for the console application. #define _WIN32_WINNT 0x0500 #include #include "CSoapClient.h" int _tmain(int argc, _TCHAR* argv[]) { CoInitialize(NULL); CSoapTCPClient m_Client; unsigned short nServerPort = 80; m_Client.SetTCPSoapServer("localhost", nServerPort); m_Client.SetSocketTimeout(2000); m_Client.SendRequest("/hellosoap/hello.asmx?op=Hello"); CoUninitialize(); return 0; } ************************************************************** SoapClient.h -------------------------------------------------------------- // File: SoapTCPClient.h #pragma once #ifndef SOAP_DEBUG_CLIENT_H_INCLUDED #define SOAP_DEBUG_CLIENT_H_INCLUDED // Includes for SoapDebugClient #ifndef _WINSOCKAPI_ #include #endif #include /////////////////////////////////////////////////////////////////// // Protocol Constants /////////////////////////////////////////////////////////////////// #define SOCKET_BACKLOG 5 #define SOCKET_BUFFER_SIZE 2048 #define SOCKET_SOAP_REQUEST_HEADER "SOAPREQ" #define SOCKET_SOAP_REQUEST_HEADER_LEN 7 #define SOCKET_SOAP_RESPONSE_HEADER "SOAPRES" #define SOCKET_SOAP_RESPONSE_HEADER_LEN 7 #define TCPSOAP_ERROR_SUCCESS 0 // OK, no error in processing #define TCPSOAP_ERROR_TRANSPORT 1 // some error occured in transport #define TCPSOAP_ERROR_PROCESSING 2 // some error occured in processing // - exception caucht or other non-SOAP thing #define TCPSOAP_ERROR_INCOMPLETE 3 // incomplete buffer ////////////////////////////////////////////////////////////////// #include #include using namespace std; class CSoapTCPClient : public ZEvtSyncSocket { protected: CString m_requestStr; CString m_responseStr; CString m_strSrvAddress; unsigned short m_nPort; SOAPCLIENT_ERROR m_errorState; CStringA m_strURL; public: CSoapTCPClient(LPCTSTR szURL = NULL) : m_strURL(CT2A(szURL)), m_errorState(SOAPCLIENT_SUCCESS) { } ~CSoapTCPClient() throw() { } SOAPCLIENT_ERROR GetClientError() { return m_errorState; } void SetClientError(SOAPCLIENT_ERROR errorState) { m_errorState = errorState; } void SetTCPSoapServer(LPCTSTR szAddr, unsigned short nPort) { m_strSrvAddress = szAddr; m_nPort = nPort; } HRESULT SendRequest(LPCTSTR tszAction) throw() { CAtlIsapiBuffer<> buffWork; ATLASSERT(tszAction != NULL); LPCSTR szAction; #ifdef UNICODE CW2A w2aAction(tszAction); szAction = w2aAction; #else szAction = tszAction; #endif if( strstr(szAction, "SOAPAction:") == szAction ) szAction += strlen("SOAPAction:"); while( *szAction == ' ') szAction++; if( m_strSrvAddress.IsEmpty() ) { cout << "No server specified. Use SetTCPSoapServer" << endl; return E_FAIL; } if( !szAction) { cout << "The SOAPAction parameter is NULL. Cannot prepare request" << endl; return E_POINTER; } // Build the request { // add header buffWork.Append(SOCKET_SOAP_REQUEST_HEADER, SOCKET_SOAP_REQUEST_HEADER_LEN); // add size DWORD dwSize; dwSize = m_strURL.GetLength(); dwSize += 1; dwSize += (DWORD)strlen(szAction); dwSize += 1; dwSize += m_requestStr.GetLength(); buffWork.Append( (LPCSTR)&dwSize, sizeof(DWORD)); buffWork.Append( (LPCSTR)m_strURL, m_strURL.GetLength() + 1); buffWork.Append( szAction, (int)strlen(szAction) + 1); buffWork.Append( (LPCSTR)m_requestStr, m_requestStr.GetLength()); } if( !Connect( (LPCTSTR)m_strSrvAddress, m_nPort) ) { cout << "Cannot connect to " << (LPCTSTR)m_strSrvAddress << ":" << m_nPort << endl; return E_FAIL; } DWORD dwWrite; dwWrite = buffWork.GetLength(); if( !Write( (const unsigned char*)(LPCSTR)buffWork, &dwWrite) ) { cout << "Error writing to the socket" << endl; return E_FAIL; } buffWork.Empty(); HRESULT hRet = S_OK; bool bKeepReading = true; { unsigned char buffRead[SOCKET_BUFFER_SIZE]; DWORD dwRead = SOCKET_BUFFER_SIZE; DWORD dwPacketSize = 0; DWORD dwError = TCPSOAP_ERROR_INCOMPLETE; while( bKeepReading) { bool bRead = Read( buffRead, &dwRead); if(!bRead) { cout << "Error reading from the socket" << endl; return E_FAIL; } buffWork.Append( (LPCSTR)buffRead, dwRead ); if( dwError == TCPSOAP_ERROR_INCOMPLETE ) { // try to parse the string if( buffWork.GetLength() >= SOCKET_SOAP_RESPONSE_HEADER_LEN + sizeof(dwError)) { // check header char header[SOCKET_SOAP_RESPONSE_HEADER_LEN + 1]; memcpy( header, (LPCSTR)buffWork, SOCKET_SOAP_REQUEST_HEADER_LEN); header[SOCKET_SOAP_REQUEST_HEADER_LEN] = '\0'; if( 0 != strcmp( header, SOCKET_SOAP_RESPONSE_HEADER)) { // stop reading and fail cout << "Incorrect transport header received : " << header << endl; bKeepReading = false; hRet = E_FAIL; } // HeaderOK< get the error const char *pdwSize = NULL; pdwSize = (LPCSTR)buffWork + SOCKET_SOAP_RESPONSE_HEADER_LEN; memcpy( &dwError, pdwSize, sizeof(dwError)); hRet = E_FAIL; switch( dwError ) { case TCPSOAP_ERROR_SUCCESS: hRet = S_OK; break; case TCPSOAP_ERROR_TRANSPORT: cout << "Socket transport error" << endl; bKeepReading = false; break; case TCPSOAP_ERROR_PROCESSING: cout << "Server processing error (non SOAP)" << endl; bKeepReading = false; break; default: cout << "Unexpected error message from the server" << endl; bKeepReading = false; break; } } } if( dwError == TCPSOAP_ERROR_SUCCESS && dwPacketSize == 0) { // error OK and the buffer size is not read yet if( buffWork.GetLength() >= SOCKET_SOAP_RESPONSE_HEADER_LEN + 2*sizeof(DWORD)) { // Get the size const char *pdwSize = NULL; pdwSize = (LPCSTR)buffWork + SOCKET_SOAP_RESPONSE_HEADER_LEN + sizeof(dwError); memcpy( &dwPacketSize, pdwSize, sizeof(dwError)); } } if( dwPacketSize > 0 ) { DWORD dwTotalSize = SOCKET_SOAP_RESPONSE_HEADER_LEN; dwTotalSize += sizeof(dwError); dwTotalSize += sizeof(dwPacketSize); dwTotalSize += dwPacketSize; // IF already read the header, the size and the buffer, then stop reading if( dwTotalSize <= buffWork.GetLength() ) bKeepReading = false; } }// end while keep reading if( hRet == S_OK ) { // no error occured LPCSTR strSrc; strSrc = (LPCSTR)buffWork + SOCKET_SOAP_RESPONSE_HEADER_LEN + 2*sizeof(DWORD); m_responseStr.Append(strSrc, dwPacketSize); } else return hRet; } return S_OK; } }; #endif// SOAP_DEBUG_CLIENT_H_INCLUDED LillyPrashanthi Sign In·View Thread·PermaLink WSDL generation error simcoe23 5:18 16 Sep '05   Hi there, I started a thread about this on the ATL forum: http://www.codeproject.com/script/comments/forums.asp?forumid=4486&select=1226191#xx1226191xx Basically, when using the HttpListnerServer, I get an error when it tries to render the WSDL. It gets to the location of the service, then throws an error from inside atlstencil.h. .... .... .... <service name="SimpleSoapAppService">             <port name="SimpleSoapAppServiceSoap" binding="s0:SimpleSoapAppServiceSoap">                   <soap:address location=" I am using VS.Net 2003 and the sample downloaded from MSDN. Any help or suggestions are appreciated. Thanks, Christopher The bomb lives only as it is falling Sign In·View Thread·PermaLink 2.00/5 (1 vote) Re: WSDL generation error simcoe23 5:46 16 Sep '05   Problem fixed. I traced it down into (atlsoap.h) method HTTP_CODE OnGetURL(). It tries to do GetServerVariable("SERVER_PORT") which hasn't been defined inside the implementation in CHttpListenerSDLGenerator. I added the following, and it generated the WSDL fine afterwards: else if( strcmp(pszVariableName, "SERVER_PORT")== 0) szVal = "333"; The bomb lives only as it is falling Sign In·View Thread·PermaLink 2.00/5 (1 vote) Source Code giving some error on compilation ashutosh_tripathi 23:13 17 Mar '05   i am running this TCPServer source code in vc7. on compilation it gives two error: 1.\TCPServer\simpleSoapSrv.h(43): error C2337: 'soap_handler' : attribute not found; it is neither a built-in nor a custom attribute that is accessible in the current namespace 2.\TCPServer\simpleSoapSrv.h(55): error C2337: 'soap_method' : attribute not found; it is neither a built-in nor a custom attribute that is accessible in the current namespace if i comment these errors then it gives error 1.TCPServer\soapDispatch.h(53): error C2259: 'ATL::CComObjectNoLock<Base>' : cannot instantiate abstract class with [ Base=SimpleSoapAppService::CSimpleSoapAppService ] can any one tell me what's problem. thanks in advance. Ashutosh Tripathi Sign In·View Thread·PermaLink 2.00/5 (2 votes) Re: Source Code giving some error on compilation dag.sanna 1:58 14 Apr '06   I did have the same problem after converting a project from VC7 to VC8. These two steps solved it for me: 1) Make sure atlbase.h is included before atlsoap.h in the stdafx.h file. 2) Make sure the following option is defined: /D_ATL_ATTRIBUTES under project properties, C/C++, Command Line, Additional Options -- modified at 6:59 Friday 14th April, 2006 Sign In·View Thread·PermaLink Re: Source Code giving some error on compilation JNRG 2:26 14 Jun '06   Cool. thanX so much for posting the solution to you problem, you saved me a lot of time, and hassles. Sign In·View Thread·PermaLink Re: Source Code giving some error on compilation dag.sanna 2:45 14 Jun '06   You're welcome. Here is one more for you that might save you even more time: http://connect.microsoft.com/feedback/ViewFeedback.aspx?FeedbackID=99486&SiteID=210 The page is regarding a problem with ATL server in VC8. To make a LONG story short, Microsoft does not prioritize Web Services on ATL server and will not fix a bug that prevents me from using it. You might find a workaround, but personally I find that it is too risky using a library that is this buggy and have no support... Sign In·View Thread·PermaLink Re: Source Code giving some error on compilation EricGen 0:30 13 Sep '06   This problem is because the soap client thinks the socket remains opened, which is silly as the server closes it once handled. You can easily get round that problem in the following way: CMyWebService service service.F(); service.m_socket.Close(); service.F(); Eric Sign In·View Thread·PermaLink Can ATL Server based Web Service do eventing Rampert 15:23 15 Nov '04   Hi Bogdan, I did some research and found some C# samples that can do eventing (server sends message back to client) through a web service created with ASP.NET. My question is "Can ATL Server created Web Service do eventing?". If so do you have any samples? We have a huge code implemented in COM, C++ so I would like to use ATL server to build our first Web Service. Thanks! Kai Sign In·View Thread·PermaLink Re: Can ATL Server based Web Service do eventing ManishTomarAMI 1:16 17 Feb '06   Hi Rampert, You said: Rampert wrote: I did some research and found some C# samples that can do eventing (server sends message back to client) through a web service created with ASP.NET. I am looking for samples like these. Can u tell me where u got them from?? Thanks in advance, Manish Sign In·View Thread·PermaLink I need to send an XML-string to a web server gorros 23:48 24 Mar '04   I need to send an xml string to a dll on the web server. The string itself is very simple, and I need no help with that. My problem is how to send it, and also how to be able to receive a status message from the server. The call (if done from a browser) look like this http://WEBSERVER/TheDLL.dll?10990|"XML-STRING" And, when processed, it will return a status code. Please, if anyone know how to do this, please give me a hint how I could go forward with this Sincerely Goran gorros Sign In·View Thread·PermaLink Server side in C# valenci 20:46 20 Mar '04   All the server-side samples (including the ones in the MS site) are CPP based. I'm looking for a recipe to make a server side C# application, that would not require any IIS installation. could you please assist. Sign In·View Thread·PermaLink 4.00/5 (2 votes) Re: Server side in C# PrasadGVL 19:10 1 Dec '04   I too have the same requirement. Any help in this regard is greatly appreciated. Thanks in advance. Sign In·View Thread·PermaLink 2.00/5 (1 vote) Re: Server side in C# Bogdan CRIVAT 19:16 1 Dec '04   Sorry, I cannot help you with this issue. You should try to post a question on the microsoft.public newsgroups (I'd say microsoft.public.dotnet.framework.aspnet or microsoft.public.dotnet.framework.aspnet.webservices) thanks, bogdan Sign In·View Thread·PermaLink Re: Server side in C# srapport 22:16 5 Jun '06   Does anybody know if there is there any webservice server code written in C# (yet) that does not require IIS? I have a client app that I'd like to publish methods from to be called via SOAP/Webservice that will run over a configurable port. Yes, this in fact this does make the client app act as a server. This is just an alternative to writing a custom messaging protocol over a socket connection. Sign In·View Thread·PermaLink 1.00/5 (1 vote) Re: Server side in C# guillaume_se 6:07 22 Jun '06   there is an official solution. and it's very simple to code. WSE v3 required. http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wse3.0/html/a59d232c-53a3-401f-82e5-2e49588923b9.asp[^] Guillaume Saint Etienne .Net expert Sign In·View Thread·PermaLink comiling with VS 2003 Stefan Leoni 23:05 6 Jan '04   for all looking for code which compiles with VS 2003 here's a link: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vcsample/html/vcsamSOAPTransportSample.asp by the way, good job SLE Sign In·View Thread·PermaLink 2.00/5 (1 vote) Launching ATL Server from C# client bobsmith2 18:50 11 Dec '03   We are looking at an architecture in which an ATL Server processing web service calls is launched from a thread (or pool of threads) within a C# client. We have prototyped simple examples and it seems to work. Our question is, can we define static objects within the C# client and have the ATL Server update these objects (since they are both threads). Can this be done? If not, is there a better alternative? Sign In·View Thread·PermaLink Adding encryption between client and server. Anonymous 12:08 26 Dec '02   Great article. I was wondering if there is anyway of hooking in the new ATL7 encryptions classes to encrypt the soap packets between client and server? Sign In·View Thread·PermaLink 5.00/5 (1 vote) Re: Adding encryption between client and server. Bogdan CRIVAT 12:38 26 Dec '02   Hello I think it should not be very hard to add encryption here. On the server side, this sample is already using a custom implementation of stream for passing the request body to the SOAP processing mechanism and for rendering the response back to the client. The stream class could be modified to decrypt the request body before passing it to the SOAP request handler and also for encrypting the response before sending it to the client (or before writing it into a file). The same encryption-enabled stream class will be used on the client side. For this, one would have to inherit from CSoapSocketClientT and change the m_writeStream member from CWriteStreamOnCString to something else that also performs the same kind of encryption that is used on the server Please let me know if I can be of any additional help Thanks, Bogdan Sign In·View Thread·PermaLink Re: Adding encryption between client and server. TommyMeng 21:48 18 Mar '03   1> Check the SOAPState Sample 2> Create a WebService Project, and enable the /Fx 3> Add soap_header and soap method into the WebService Project. 4> Compile the WebService Project 5> Create a ATL EXE or Service Project(No Attributes), add the Soap Interface into idl file, and add a class to implement the interface. 6> Copy the content of the expansion file form WebService project into the class. 7> Here you go, you also got the soap_header... Sign In·View Thread·PermaLink 5.00/5 (1 vote) Re: Adding encryption between client and server. TommyMeng 21:48 18 Mar '03   1> Check the SOAPState Sample 2> Create a WebService Project, and enable the /Fx 3> Add soap_header and soap method into the WebService Project. 4> Compile the WebService Project 5> Create a ATL EXE or Service Project(No Attributes), add the Soap Interface into idl file, and add a class to implement the interface. 6> Copy the content of the expansion file form WebService project into the class. 7> Here you go, you also got the soap_header... Tommy Meng Sign In·View Thread·PermaLink Requirements for PocketPc Anonymous 9:56 4 Nov '02   Has anyone tried to compile the sample for WindowsCe, though i am not sure this can be done. Sign In·View Thread·PermaLink

Last Visit: 14:48 9 Jul '09     Last Update: 14:48 9 Jul '09 12 Next »