didnt understand?
will you please eloborate??
On Mon, Dec 26, 2011 at 8:52 AM, Matthew Sherborne <msherbo...@gmail.com>wrote:
> probably a good starting point would be to read some of the code here:
> https://github.com/matiu2/Wt/blob/master/src/http/Connection.h
>
> On Mon, Dec 26, 2011 at 12:48 PM, Mohammed Rashad <
> mohammedrasha...@gmail.com> wrote:
>
>>
>>
>> On Thu, Dec 22, 2011 at 1:17 PM, Koen Deforche <k...@emweb.be> wrote:
>>
>>> Hey Mohammed,
>>>
>>> 2011/12/22 Mohammed Rashad <mohammedrasha...@gmail.com>:
>>> > Dear Koen,
>>> > I have couple of questions after going through NaCl web site and demos
>>> from
>>> > CWS
>>> > NaCal act as an SDK or toolkit.
>>> > NaCl can use wthttp connector right?
>>>
>>> Probably not, or at least that is not what we would want.
>>>
>>> What you want is to be able to link an application (let's say, the
>>> widgetset feature example), link it against a wtnacl library in order
>>> to get a hello.nexe NaCl binary.
>>>
>>> When embedding this binary into an HTML page as a type
>>> "application/x-nacl-srpc" embedded object, then acting as a widget set
>>> application, the hello.nexe application will render into a div by
>>> communicating over the JavaScript-to-NaCl communication bridge (which
>>> is called SRPC). In this way. Thus instead of :
>>>
>>> browser --- HTTP --- wthttp --- wt application
>>> browser --- srpc --- wtnacl --- wt application
>>>
>> so what I need to build is wtnacl right?
>> wtnacl will link with libwt and nacl lib
>> it outputs nexe
>>
>> upto here its easy . just linking
>>
>> the real fun will maybe here...
>> instead of writing a javascript code we need to execute wt code
>> and hello.nexe which is linked with google nacl and libwt*.so
>> is embedded inside .wt file
>>
>> i think there will be no problem if change .nexe to .wt
>> the wtnacl will act as a communication link between wt and nacl, right?
>>
>> also I need to know a wthttp connector works,
>>
>> Can anyone tell me how. I need to know its internals
>>
>> Thanks in Advance
>>
>>>
>>> See also: http://www.chromium.org/nativeclient/how-tos/simple-rpc
>>>
>>> Regards,
>>> koen
>>>
>>
>>
>>
>> --
>> Regards,
>> Rashad
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Write once. Port to many.
>> Get the SDK and tools to simplify cross-platform app development. Create
>> new or port existing apps to sell to consumers worldwide. Explore the
>> Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join
>> http://p.sf.net/sfu/intel-appdev
>> _______________________________________________
>> witty-interest mailing list
>> witty-interest@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/witty-interest
>>
>>
>
>
> ------------------------------------------------------------------------------
> Write once. Port to many.
> Get the SDK and tools to simplify cross-platform app development. Create
> new or port existing apps to sell to consumers worldwide. Explore the
> Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join
> http://p.sf.net/sfu/intel-appdev
> _______________________________________________
> witty-interest mailing list
> witty-interest@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/witty-interest
>
>
--
Regards,
Rashad
------------------------------------------------------------------------------
Write once. Port to many.
Get the SDK and tools to simplify cross-platform app development. Create
new or port existing apps to sell to consumers worldwide. Explore the
Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join
http://p.sf.net/sfu/intel-appdev
_______________________________________________
witty-interest mailing list
witty-interest@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/witty-interest
