% This data is distributed under the terms of the Open Data Commons Attribution License (ODC-By) v1.0 - See more at: http://opendatacommons.org/licenses/by/1-0/ % Volume 3, Issue 1, 2016 @Article{OJCC_2016v3i1n02_YingweiWang, title = {Definition and Categorization of Dew Computing}, author = {Yingwei Wang}, journal = {Open Journal of Cloud Computing (OJCC)}, issn = {2199-1987}, year = {2016}, volume = {3}, number = {1}, pages = {1--7}, url = {http://nbn-resolving.de/urn:nbn:de:101:1-201705194546}, urn = {urn:nbn:de:101:1-201705194546}, publisher = {RonPub}, bibsource = {RonPub}, abstract = {Dew computing is an emerging new research area and has great potentials in applications. In this paper, we propose a revised definition of dew computing. The new definition is: Dew computing is an on-premises computer software-hardware organization paradigm in the cloud computing environment where the on-premises computer provides functionality that is independent of cloud services and is also collaborative with cloud services. The goal of dew computing is to fully realize the potentials of on-premises computers and cloud services. This definition emphasizes two key features of dew computing: independence and collaboration. Furthermore, we propose a group of dew computing categories. These categories may inspire new applications.} } @Article{OJCC_2016v3i1n02_Fisher, title = {Doing More with the Dew: A New Approach to Cloud-Dew Architecture}, author = {David Edward Fisher and Shuhui Yang}, journal = {Open Journal of Cloud Computing (OJCC)}, issn = {2199-1987}, year = {2016}, volume = {3}, number = {1}, pages = {8--19}, url = {http://nbn-resolving.de/urn:nbn:de:101:1-201705194535}, urn = {urn:nbn:de:101:1-201705194535}, publisher = {RonPub}, bibsource = {RonPub}, abstract = {While the popularity of cloud computing is exploding, a new network computing paradigm is just beginning. In this paper, we examine this exciting area of research known as dew computing and propose a new design of cloud-dew architecture. Instead of hosting only one dew server on a user's PC - as adopted in the current dewsite application - our design promotes the hosting of multiple dew servers instead, one for each installed domain. Our design intends to improve upon existing cloud-dew architecture by providing significantly increased freedom in dewsite development, while also automating the chore of managing dewsite content based on the user's interests and browsing habits. Other noteworthy benefits, all at no added cost to dewsite users, are briefly explored as well.} }