2

在我的项目中，我使用 volley 下载我解析并显示在列表视图中的 JSON 流。我使用以下方法加载我的数据：

private void loadEventData(int year, final int month) {

    // get volley request queue
    requestQueue = cpcApplication.getRequestQueue(getActivity());

    String url = "****************?year=" + year
            + "&month=" + month;

    pd = ProgressDialog.show(getActivity(), "Loading Events", "Retrieving Data from Server");
    pd.setCancelable(true);

    JsonObjectRequest jr = new JsonObjectRequest(Request.Method.GET, url, null, new Response.Listener<JSONObject>() {

        @Override
        public void onResponse(JSONObject response) {

            Log.i(TAG, response.toString());

            // parse the incoming response
            parseJson(response, month);

            // notify the listview that the data set has changed
            adapter.notifyDataSetChanged();

            // set the listview at the top position
            listView.setSelection(current.get(Calendar.DAY_OF_MONTH));

            // dismiss the ProgressDialog
            pd.dismiss();

        }
        }, new Response.ErrorListener() {

        @Override
        public void onErrorResponse(VolleyError error) {

            error.printStackTrace();

            // cancel the progress dialog
            pd.dismiss();

            // let the user know that a network connection is not available
            Toast.makeText(getActivity(), "Cannot communicate with server.  Check network connection.", Toast.LENGTH_LONG).show();
        }

    });

    // add the network request to the queue
    requestQueue.add(jr);

}

对这个方法的第一次调用效果很好。在第二次通话中，我收到超时错误。当我使用以下命令时：

jr.setRetryPolicy(new DefaultRetryPolicy(
            2500, DefaultRetryPolicy.DEFAULT_TIMEOUT_MS, DefaultRetryPolicy.DEFAULT_BACKOFF_MULT));

为了增加请求的时间量，请求需要超过 30 秒并产生以下日志输出：

10-19 20:53:19.746: D/Volley(17523): [2786] BasicNetwork.logSlowRequests: HTTP response for request=<[ ] http://************ 0x63ea5535 NORMAL 1> [lifetime=41769], [size=5467846], [rc=200], [retryCount=2]
10-19 20:53:19.796: D/dalvikvm(17523): GC_CONCURRENT freed 7462K, 26% free 24424K/33000K, paused 6ms+4ms, total 56ms
10-19 20:53:19.796: D/dalvikvm(17523): WAIT_FOR_CONCURRENT_GC blocked 51ms
10-19 20:53:19.826: I/dalvikvm-heap(17523): Grow heap (frag case) to 35.123MB for 10935708-byte allocation
10-19 20:53:19.857: D/dalvikvm(17523): GC_FOR_ALLOC freed 3K, 20% free 35100K/43680K, paused 23ms, total 28ms
10-19 20:53:19.917: D/dalvikvm(17523): GC_CONCURRENT freed 2018K, 19% free 35816K/43680K, paused 3ms+4ms, total 60ms
10-19 20:53:20.007: D/dalvikvm(17523): GC_CONCURRENT freed 4874K, 15% free 37226K/43680K, paused 2ms+3ms, total 27ms
10-19 20:53:20.007: D/dalvikvm(17523): WAIT_FOR_CONCURRENT_GC blocked 24ms
10-19 20:53:20.067: D/dalvikvm(17523): GC_FOR_ALLOC freed 5037K, 15% free 38601K/44900K, paused 19ms, total 19ms
10-19 20:53:20.117: D/dalvikvm(17523): GC_FOR_ALLOC freed 4680K, 14% free 40045K/46564K, paused 20ms, total 20ms
10-19 20:53:20.177: D/dalvikvm(17523): GC_FOR_ALLOC freed 5576K, 14% free 41572K/48272K, paused 20ms, total 20ms
10-19 20:53:20.227: D/dalvikvm(17523): GC_FOR_ALLOC freed 6133K, 15% free 43406K/50548K, paused 20ms, total 20ms
10-19 20:53:20.287: D/dalvikvm(17523): GC_CONCURRENT freed 6486K, 15% free 45029K/52428K, paused 2ms+2ms, total 24ms
10-19 20:53:20.287: D/dalvikvm(17523): WAIT_FOR_CONCURRENT_GC blocked 11ms
10-19 20:53:20.407: D/Volley(17523): [1] Request.finish: 42553 ms: [ ] http://****** 0x63ea5535 NORMAL 1

当我在浏览器中执行相同的请求时，只需要几秒钟。为什么延迟和令人难以置信的内存消耗？

4

3 回答 3

5

每次调用您创建的新方法RequestQueue都是不推荐的方法。您应该创建一个RequestQueue，可能是一个公开可见的单例，在创建应用程序时初始化一次。

尝试移动RequestQueue外部，看看它是否能解决您的问题。

于 2013-10-20T16:23:42.320 回答
2

我有一些问题：

Volley.newRequestQueue(getApplicationContext());

它导致某些手机在启动时的第一个请求需要很长时间。我将其更改为：

Cache cache = new DiskBasedCache(getCacheDir(), 1024 * 1024);
Network network = new BasicNetwork(new HurlStack());
mRequestQueue = new RequestQueue(cache, network);
mRequestQueue.start();

这解决了我的问题。

于 2016-02-14T15:04:15.903 回答
0

我正在尝试用很少的代码来解释（已经简要解释了 Itai）

下面的代码解释了如何将 Volley 的全局请求队列与应用程序类的单例实例一起使用，以便在其他地方轻松访问，并使代码更节省内存！

公共类 ApplicationController 扩展应用程序 {

/**
 * Log or request TAG
 */
public static final String TAG = "VolleyPatterns";

/**
 * Global request queue for Volley
 */
private RequestQueue mRequestQueue;

/**
 * A singleton instance of the application class for easy access in other places
 */
private static ApplicationController sInstance;

@Override
public void onCreate() {
    super.onCreate();

    // initialize the singleton
    sInstance = this;
}

/**
 * @return ApplicationController singleton instance
 */
public static synchronized ApplicationController getInstance() {
    return sInstance;
}

/**
 * @return The Volley Request queue, the queue will be created if it is null
 */
public RequestQueue getRequestQueue() {
    // lazy initialize the request queue, the queue instance will be
    // created when it is accessed for the first time
    if (mRequestQueue == null) {
        mRequestQueue = Volley.newRequestQueue(getApplicationContext());
    }

    return mRequestQueue;
}

/**
 * Adds the specified request to the global queue, if tag is specified
 * then it is used else Default TAG is used.
 * 
 * @param req
 * @param tag
 */
public <T> void addToRequestQueue(Request<T> req, String tag) {
    // set the default tag if tag is empty
    req.setTag(TextUtils.isEmpty(tag) ? TAG : tag);

    VolleyLog.d("Adding request to queue: %s", req.getUrl());

    getRequestQueue().add(req);
}

/**
 * Adds the specified request to the global queue using the Default TAG.
 * 
 * @param req
 * @param tag
 */
public <T> void addToRequestQueue(Request<T> req) {
    // set the default tag if tag is empty
    req.setTag(TAG);

    getRequestQueue().add(req);
}

/**
 * Cancels all pending requests by the specified TAG, it is important
 * to specify a TAG so that the pending/ongoing requests can be cancelled.
 * 
 * @param tag
 */
public void cancelPendingRequests(Object tag) {
    if (mRequestQueue != null) {
        mRequestQueue.cancelAll(tag);
    }
} }

对于完整的实现参考这个博客

致谢：Arnab Chakraborty

于 2014-02-13T06:15:44.700 回答