cancel
Showing results for 
Search instead for 
Did you mean: 
SOLVED

Unix Sockets in .NET/Http web api in core

Unix Sockets in .NET/Http web api in core

WEI_You
Established Member

I want build a backend service in my app,Custom API and unix sockets by .NET or Go

,I can built in in windows and use web service,but I don't know how to built in core's app enviornment and install in CtrlX3,are there have some knowledge or sample demo? I can't find this type sample in SDK,there just have front-end service

 

3 REPLIES 3

Sgilk
Contributor

Hello @WEI_You ,

Here is an example web server utilizing unix sockets implemented in Go.

Go Webserver Example 

Here is an ASP.NET example.

Generally, here is some information on getting started with development for ctrlX OS.

Getting Started 

WEI_You
Established Member

hello Sgilk:

thanks for your ansewr,

I had try test .net unix socket success in app development enviroment,and build & install in ctrlX core.there have some question,

I think app maybe have three part:logical,sever(backend service), front-end service(html page)

1. Is it necessary for the unix socket severto have a proxy mapping(mianfest file) ,if the app don't have  front-end service?

2.whether backend service can have the Custom  rest api (like API reference) provide for other  PC client

3.the Communication method between front-end and back-end?unix socket,rest api or other?

there are my  test code of unix socket sever,may be I need a html page to display(as front-end service) in the next step?

WEI_You_0-1703039897075.png

WEI_You_1-1703039935878.png

Hi @WEI_You ,

1. The proxy mapping will be necessary if there is to be any communication with the application from outside of the localhost. If you are making REST API calls from a PC client like you describe in #2, you will need proxy mapping in the package manifest.

2. Absolutely. You can create your own API reference and make custom calls to your application server.

3. You can set this up however you'd like. Usually, if the application is running locally, you can use Unix Sockets. Otherwise, you'd use TCP. Here is an example showing both methods.

Regarding your test code, a front end isn't required. You can do whatever you'd like here to fit your requirements.

Icon--AD-black-48x48Icon--address-consumer-data-black-48x48Icon--appointment-black-48x48Icon--back-left-black-48x48Icon--calendar-black-48x48Icon--center-alignedIcon--Checkbox-checkIcon--clock-black-48x48Icon--close-black-48x48Icon--compare-black-48x48Icon--confirmation-black-48x48Icon--dealer-details-black-48x48Icon--delete-black-48x48Icon--delivery-black-48x48Icon--down-black-48x48Icon--download-black-48x48Ic-OverlayAlertIcon--externallink-black-48x48Icon-Filledforward-right_adjustedIcon--grid-view-black-48x48IC_gd_Check-Circle170821_Icons_Community170823_Bosch_Icons170823_Bosch_Icons170821_Icons_CommunityIC-logout170821_Icons_Community170825_Bosch_Icons170821_Icons_CommunityIC-shopping-cart2170821_Icons_CommunityIC-upIC_UserIcon--imageIcon--info-i-black-48x48Icon--left-alignedIcon--Less-minimize-black-48x48Icon-FilledIcon--List-Check-grennIcon--List-Check-blackIcon--List-Cross-blackIcon--list-view-mobile-black-48x48Icon--list-view-black-48x48Icon--More-Maximize-black-48x48Icon--my-product-black-48x48Icon--newsletter-black-48x48Icon--payment-black-48x48Icon--print-black-48x48Icon--promotion-black-48x48Icon--registration-black-48x48Icon--Reset-black-48x48Icon--right-alignedshare-circle1Icon--share-black-48x48Icon--shopping-bag-black-48x48Icon-shopping-cartIcon--start-play-black-48x48Icon--store-locator-black-48x48Ic-OverlayAlertIcon--summary-black-48x48tumblrIcon-FilledvineIc-OverlayAlertwhishlist