Hi ,

Yes, I agree with you. I updated project structure[1]
<https://github.com/GPrathap/REST_API_in_C> as you said.

Thank you.


Geesara Prathap Kulathunga,
Software Engineering Intern,
University of Peradeniya.
[email protected] <Email:[email protected]>
+940772684174


On Fri, Feb 13, 2015 at 11:04 PM, Prabath Abeysekera <[email protected]>
wrote:

> Hi Geesara,
>
> Sorry, I just managed to read up on this. What if we go for something
> similar to the following structure?
>
> ├── bin                                         -> Executables (if any)
> ├── conf                                       -> Configuration files
> ├── src                                         -> All source files
> │       └── controllers
> │                    └── signUp.c
> │       └── routes
> │                    └── routing_index.c
> ├── resources
> │          └── keystore                     -> Keystores configs
> ├── libs                                         -> External libraries
> │
> ├── test                                         -> Test cases
> │        ├── generateUsers.js
> │        ├── test.js
> │        └── user.js
> ├── MAKEFILE                             -> MAKEFILE to build the project
> ├── README.txt                           -> Instructions to deploy the
> module
>
> Cheers,
> Prabath
>
> On Tue, Feb 10, 2015 at 10:33 AM, Geesara Prathap <[email protected]>
> wrote:
>
>> Restructuring project
>>
>> Hi,
>>
>> Project structure
>>
>> ----------------------------------------------------------------------------------------------------
>> ├── bin                       -> makefile and configuration files
>> ├── controllers           -> all control functions are in this directory
>> │   └── signUp.c        -> ex:signUp|login|addApplication|...
>> ├── keys                   -> public and private keys
>> ├── libs                      -> libraries are used
>> │   └── externalLibs    -> external libraries
>> ├── routes                 -> routers in rest api
>> │   └── routing_index.c -> this is the one that handle all routers
>> └── test                     -> api testing
>>     ├── generateUsers.js
>>     ├── test.js
>>     └── user.js
>>
>> I just created a new project structure 
>> :https://github.com/GPrathap/REST_API_in_C
>>
>>
>> How about this way ?
>>
>> Thanks,
>>
>>
>>
>> Geesara Prathap Kulathunga,
>> Software Engineering Intern,
>> University of Peradeniya.
>> [email protected] <Email:[email protected]>
>> +940772684174
>>
>>
>> On Tue, Jan 6, 2015 at 3:43 PM, Geesara Prathap <[email protected]> wrote:
>>
>>> Hi,
>>>
>>> There is a Node server which acts as a hub  among devices,clients  and
>>> WSO2 API Manager.
>>>
>>> As of now the Client is able to,
>>>
>>>    1. sign up
>>>    2. login
>>>    3. add  applications
>>>    4. subscribe to applications
>>>    5. get the access token from API Manager
>>>
>>>  through Node server.
>>>
>>> When adding an application, client is able to configure how devices are
>>> arranged and that configuration file should be sent to the node server with
>>> a client request. Then Node server reads that file and generates a REST API
>>> with respect to the relevant client.
>>>
>>>
>>>
>>> I did the first part of this implementation. Now a client can do all
>>> those operations which were  mentioned above except REST API generation
>>> part. Here is the code repository[1]  what I did so far.
>>>
>>> [1] https://github.com/GPrathap/wso2nodeserver
>>>
>>>
>>>
>>> Thanks
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> Geesara Prathap Kulathunga
>>> Software Engineer Intern
>>> University of Peradeniya
>>> [email protected] <Email:[email protected]>
>>> +940772684174
>>>
>>>
>>
>
>
> --
> Prabath Abeysekara
> Associate Technical Lead, Data TG.
> WSO2 Inc.
> Email: [email protected]
> Mobile: +94774171471
>
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to