QT mobile and gSOAP

[arjoshi]

Greetings from a newbie to mobile app / QT developer.:

I have questions concerning building a mobile application that talks to a SOAP server. However, there is a prologue to my question:

PROLOGUE TO THE QUESTIONS BEGINS:
================================================== ==========================
[1] A non-mobile(desktop based) application could have an architecture as follows:

Software Stack:
-------------------------
QT (Fat Client) <=> internet <=> SOAP Server<=> business logic<=>Database.

Hardware Stack:
-------------------------
The hardware required is a computer connected to the internet,
internet<=>Physical Machine (hosting the soap server and the database)

[2] A mobile sms - based application

Software Stack( and I could stand corrected on this) :
-------------------
QT (Fat Cient) <=> sms gateway <=>SOAP Server<=> business logic<=>Database.
Hardware Stack:
-----------------------
mobile_phone<=>GSM Modem<=>Physical Machine (hosting the soap server and the database)

================================================== =========================
PROLOGUE TO THE QUESTIONS ENDS

Having said and done this, Coming to the main question of this post:

[1] What would be the hardware/software stack for a fat client application (written in QT) on a mobile phone to talk to a soap server installed on a PC connected to the internet. ?


Thanking you in advance for your time,.

-AJ

[David_G_Ortega]

Hi,

its quite difficult to answer you!! I have not understand so much!!

Do you actually need help to use gSoap in Qt?
Do you need help to communicate from a Qt app to a gSoap one?

I can point you in both directions since I have intensively developed using Qt and gSoap.

Using gSoap in QT (a sample code)...

#include "src/gsoap/soapOtalierService.h"
 
int main(int argc, char *argv[])
{
	QApplication a(argc, argv);
 
	int            soapMessage = SOAP_OK;
	std::string    queryString = getenv("QUERY_STRING");
	OtalierService service;
 
	if(queryString == "wsdl")
	{
	    service.http_content = "text/xml";
	    soap_response(&service, SOAP_FILE);
 
	    FILE *fd      = 0;
	    fd            = fopen("Otalier.wsdl", "rb");
	    bool fileRead = true;
	    while(fileRead)
	    {
	        size_t r = fread(service.tmpbuf, 1, sizeof(service.tmpbuf), fd);
	        if (!r || soap_send_raw(&service, service.tmpbuf, r))
	        {
	            fileRead = false;
	        }
	    }
 
	    fclose(fd);
	    soap_end_send(&service);
 
	}else
	{
	    //soap_set_omode(&service, SOAP_C_UTFSTRING);
	    service.serve();
	}
 
	QTimer::singleShot(0, qApp, SLOT(quit()));
	a.exec();
 
	return soapMessage;
}

#include "src/gsoap/soapOtalierService.h"

int main(int argc, char *argv[])
{
	QApplication a(argc, argv);

	int            soapMessage = SOAP_OK;
	std::string    queryString = getenv("QUERY_STRING");
	OtalierService service;

	if(queryString == "wsdl")
	{
	    service.http_content = "text/xml";
	    soap_response(&service, SOAP_FILE);

	    FILE *fd      = 0;
	    fd            = fopen("Otalier.wsdl", "rb");
	    bool fileRead = true;
	    while(fileRead)
	    {
	        size_t r = fread(service.tmpbuf, 1, sizeof(service.tmpbuf), fd);
	        if (!r || soap_send_raw(&service, service.tmpbuf, r))
	        {
	            fileRead = false;
	        }
	    }

	    fclose(fd);
	    soap_end_send(&service);

	}else
	{
	    //soap_set_omode(&service, SOAP_C_UTFSTRING);
	    service.serve();
	}

	QTimer::singleShot(0, qApp, SLOT(quit()));
	a.exec();

	return soapMessage;
}

To copy to clipboard, switch view to plain text mode 

The code speaks by itself the trick using Qt and events is in using

QTimer::singleShot(0, qApp, SLOT(quit()));
a.exec();

which is going to do only an execution of the code and terminate the whole thing, the rest is the gSoap code needed. The executable is served as a cgi with apache.

To communicate the QT app with a gSoap service can be done in some ways, one could be write the entire SOAP XML request and make a request to the service. The other aproach is write a client using gsoapcpp2 and the last one is just passing cgi vars, I used the last one at my first atempt but later on I became more sophisticated

Hope this helps