We are adventuring into the land of Web Services. Here is a simple breakdown
of the architecture:
1) Accept XML data
2) For each node, perform the related data operation in our backend.
3) Return a success/error code.
Pretty simple design. We have a need to accept large amounts of XML data to
our web service (50+ meg raw data). We are running into issues with the
aspnet_wp recycling itself because of memory consumption on our dev box. Is
there a practical limit to the amount of data I can except to work with on a
single post?
Since we perform our data operations per node, can we use an asynchronous
methods?
1) Get the incoming node
2) Perform our data operation
3) Clean up the resources of the node
My thinking is if we can clean up the each node as we go, it can help with
the memory consumtion we are experiencing.
Any advice or thoughts welcome.
of the architecture:
1) Accept XML data
2) For each node, perform the related data operation in our backend.
3) Return a success/error code.
Pretty simple design. We have a need to accept large amounts of XML data to
our web service (50+ meg raw data). We are running into issues with the
aspnet_wp recycling itself because of memory consumption on our dev box. Is
there a practical limit to the amount of data I can except to work with on a
single post?
Since we perform our data operations per node, can we use an asynchronous
methods?
1) Get the incoming node
2) Perform our data operation
3) Clean up the resources of the node
My thinking is if we can clean up the each node as we go, it can help with
the memory consumtion we are experiencing.
Any advice or thoughts welcome.