Strictly necessary cookies are on by default and cannot be turned off. Functional, Performance and Tracking/targeting/sharing cookies can be turned on below based on your preferences (this banner will remain available for you to accept cookies). You may change your cookie settings by deleting cookies from your browser. Then this banner will appear again. You can learn more details about cookies HERE.
Strictly necessary (always on)
Functional, Performance and Tracking/targeting/sharing (default off)
There is a difference between Xively, AWS, etc and the http webserver running on Wiced device.
Xively and services like Xively create a connection between their (Xively) server and the Wiced device in question. User connects to Xively server and Xively server connects to the Wiced device and exchange data. In this case the http server running on the Xilvely server and the Xively client running on the Wiced device.
For Wiced http webserver case, user directly connects to the Wiced device and exchange data over the http server running on the Wiced device. There is no middle man in place the exchange data securely.
To access the http server running on the Wiced device, user needs to be on the same network as the Wiced device is connected or router allows users to access the http server running on the Wiced device outside of the private network. This is simply a setup of the router and perhaps optionally getting registered on the DNS server. Perhaps this article Web Server Setup Behind a Router or similar one would help you to setup your network.
I believe you can use port forwarding, which as Seyhan mentioned, you would need to set up in your router. You might run into trouble if your ISP dynamically assigns you an IP, or if they assign multiple people to your IP.