Hi, e-tag,

Many thanks for your comments!


On November 11, 2014 4:31:39 PM GMT+08:00, e-tge <t...@e-tge.de> wrote:
>
>Even if not being asked directly, I comment :-)
>
>The simple built-in HTTP server runs quite OK (I've been using it in a
>project for years meanwhile), only:
>- as stated earlier I adopted a couple of fixes from that google code 
>  side project, testing with valgrind is a good idea (problematic on 
>  ARM though) to find memory leaks
>- using different ports is no problem at all (from the Axis2c 
>  perspective)
>
>HTH tge :-)
>
>On Mo, 2014-11-10 at 21:52 +0700, Woody Wu wrote:
>> Hi, Stadelmann
>> 
>> 
>> How do you thing about the option (a) if I run lighttpd only for
>those
>> not so many static web pages on my device and run axis2/c only for
>> providing web services for my non-browser clients that run on PC? The
>> axis/2 and lighttpd could be running on totally separated http ports?
>> Do you think it's feasible?
>> 
>> 
>> On Tuesday, 4 November 2014, Stadelmann Josef
>> <josef.stadelm...@axa-winterthur.ch> wrote:
>>         AFAIK
>>         I think you have two options with Axis2/C
>>         
>>         a) a simple standalone http server (was called not production
>>         quality in the past)
>>         b) axis2/C as a module, which is then engaged/called by
>apache
>>         webserver, to be adapted for lighttpd
>>         
>>         Then I think you need to have a closer look at where and what
>>         and how apache web server engages/calls the axis2 module.
>>         Then if you understand that, learn how lighttpd adapts a
>>         module, start with something very simple, then take the
>>         relevant axis2/C
>>         code/module to match/fit into your  lighttpd web server as a
>>         module.
>>         
>>         So  - dive deep into lighttpd and read
>>        
>http://redmine.lighttpd.net/projects/1/wiki/HowToWriteALighttpdPlugin
>>         because that is what you have to do anyway;
>>         
>>         In my mind you will very likely end up building your lighttpd
>>         yourself from source code.
>>         
>>         Josef (without knowing lighttpd but said this from a raw
>>         architecture point of view)
>>         
>>         
>>         
>>         -----Original Message-----
>>         From: Woody Wu [mailto:narkewo...@gmail.com]
>>         Sent: Montag, 3. November 2014 14:58
>>         To: Apache AXIS C User List; e-tge
>>         Subject: Re: axis2/c on ARM with lighttpd
>>         
>>         
>>         
>>         On November 3, 2014 5:00:20 PM GMT+08:00, e-tge <t...@e-tge.de>
>>         wrote:
>>         >
>>         >A few months ago I built Axis2C natively (i.e. directly on
>an
>>         ARM Linux
>>         >sys!) w/o any problems as far as I can remember. Works the
>>         usual way:
>>         >1. Unpack sources
>>         >2. ./configure
>>         >3. make
>>         >done.
>>         >Possibly some build tools must be installed first.
>>         >
>>         >I never did any cross-compiling, hence cannot say anything
>>         about this,
>>         >but would expect that this is basically a matter of
>>         specifying the
>>         >right compiler flags (?) When running configure (use --help)
>>         you can
>>         >set compiler flags.
>>         >
>>         That's a good news to me, sounds likely.  Thanks!
>>         
>>         >Regarding lighttpd - no idea, but would be interesting to me
>>         too.
>>         >Axis2c
>>         >has an apache integration, so assuming lighthttpd supports
>>         the same
>>         >module extension mechanism, it's probably the same/similar
>>         >
>>         >HTH :-)
>>         >  tge
>>         >
>>         
>>         What modules that axis2/c requires from apache?
>>         
>>         >On So, 2014-11-02 at 16:13 +0800, Woody Wu wrote:
>>         >> Hi,
>>         >>
>>         >> I want to choose a web service engine workable on my ARM
>>         +lighttpd
>>         >environment.  For axis2/c, it requires that axis2/c can be
>>         cross
>>         >compiled for ARM and that the axis2/c does not require
>apache
>>         httpd
>>         >itself as web server. Since I am quite new to axis2/c, could
>>         some be
>>         >kind to clarify theses points for me?
>>         >>
>>         >> Thanks in advance.
>>         >>
>>         >> -woody, sent from mobile
>>         >>
>>         >>
>>        
>---------------------------------------------------------------------
>>         >> To unsubscribe, e-mail: c-user-unsubscr...@axis.apache.org
>>         >> For additional commands, e-mail:
>>         c-user-h...@axis.apache.org
>>         >>
>>         
>>         -woody, sent from mobile
>>         
>>        
>---------------------------------------------------------------------
>>         To unsubscribe, e-mail: c-user-unsubscr...@axis.apache.org
>>         For additional commands, e-mail: c-user-h...@axis.apache.org
>>         
>> 
>> 
>> -- 
>> Sent from Gmail Mobile

-woody, sent from mobile

---------------------------------------------------------------------
To unsubscribe, e-mail: c-user-unsubscr...@axis.apache.org
For additional commands, e-mail: c-user-h...@axis.apache.org

Reply via email to