8 Matching Annotations
  1. Jul 2023
    1. A different application of the downstream collector is to do a secondary groupingBy to the results of the first group by.

      不但可以 groupingBy(BlogPost::getAuthor, groupingBy(BlogPost::getType) 分组之后再分组;还可以 分组之后,再映射 groupingBy(BlogPost::getAuthor, tomap(BlogPost::getType,BlogPost::xxx) 第二个参数可以跟任何 collectors 里面的操作

  2. Mar 2023
  3. Mar 2022
  4. Dec 2020
  5. Oct 2020
    1. Improving the way to Communicate Learning Activities to an Informal Learning Collector

      CASAÑ, M. J., HIERRO, N., GALANIS, N., MAYOL, E., & ALIER, M. (2015). Improving the way to Communicate Learning Activities to an Informal Learning Collector. International Journal of Engineering Education, 31(3), 874–883.

      https://search.ebscohost.com/login.aspx?direct=true&AuthType=shib&db=eue&AN=103081819&site=eds-live&scope=site&custid=uphoenix

      Lifelong Learning has been a growing interest in e-learning research communities, in a similar way as other related kinds of learning (formal, non-formal and informal) already had. In fact, the Tagging Recognition and Acknowledgment of Informal Learning Experiences project proposes a framework to manage these types of learning, giving special attention to informal learning. This project gathers informal learning activities with an Informal Learning Collector. The main way for registering informal learning activities data into the Informal Learning Collector is using push mechanisms where the user explicitly introduces such information. In this paper, we present some evaluation of user opinions about this push communication mechanism, and propose an alternative way to communicate informal learning activities data, by using a pull mechanism. Using the pull mechanism, the Informal Learning Collector collects data directly from external applications. After the introduction of the pull mechanism, Informal Learning Collector users have confirmed that usability has been improved significantly.

  6. Jun 2020
  7. Jan 2014
    1. This sketch is complicated by the fact that there are actually three such arenas; the CLR collector is generational. Objects start off in the “short lived” heap. If they survive they eventually move to the “medium lived” heap, and if they survive there long enough, they move to the “long lived” heap. The GC runs very often on the short lived heap and very seldom on the long lived heap; the idea is that we do not want to have the expense of constantly re-checking a long-lived object to see if it is still alive. But we also want short-lived objects to be reclaimed swiftly.