How to read remote device directories' names (using socket)

[garrygar]

Hello,

I am pretty new to Symbian and I would highly appreciate if you guys could get me out of this. I have been doing a bit of research but don't know how to start it.

I have an application on two different devices (same application) and the basic idea is that I want to see directory names of device A on device B on lets say in C drive or file list in hard coded folder 'foo' which is in 'c\data\foo'. The socket part is done already i.e. the socket is established between the two devices. The thing that I have understood so far is that I have to use Serialization and DeSerialization i.e. ExternalizeL() and InternalizeL(). But I have no idea how should I start with it. A push or pointer (or more) would be highly appreciated in getting me out of this.

I went throught this http://discussion.forum.nokia.com/fo...d.php?t=101769 and other posts but I don't know how much does it help my case.

And Would I need to Build and Parse a message containing the data or Externalize and Internalize will do that for me?

Thanks.

Garry

[wizard_hu_]

Since the combined length of - say - filenames in a directory can vary a lot, serialization is a good idea.
On the sender side you could make use of an RBufWriteStream with a CBufFlat. After serialization, you know the length, that is what you should send to the receiver side first:

CBufFlat *buf=CBufFlat::NewL(10);
CleanupStack::PushL(buf);
RBufWriteStream stream;
stream.Open(*buf);
stream.PushL();
// serialize your data here
stream.CommitL();
CleanupStack::PopAndDestroy(); // stream

TPckgBuf<TInt> size; // TPckgBuf is a 8-bit descriptor, containing an instance of the type specified as the template argument
size()=buf->Size();  // TPckgBuf::operator() provides access to the contained object

TRequestStatus stat;
socket.Write(stat,size);
User::WaitForRequest(stat);
User::LeaveIfError(stat);

socket.Write(stat,buf->Ptr());
User::WaitForRequest(stat);
User::LeaveIfError(stat);

CleanupStack::PopAndDestroy(); // buf

Of course this code is nasty, because using User::WaitForRequest blocks your whole application. So in reality and active object should be used, but for testing purposes the code actually works, and it is more readable this way.

On the receiver side you get "size" first, then you should read exactly the same amount of data from the socket. It is tricky a bit, because creating a descriptor of specified size in runtime is a bit tricky:

TPckgBuf<TInt> size;

TRequestStatus stat;
socket.Read(stat,size);
User::WaitForRequest(stat);
User::LeaveIfError(stat);

HBufC8 *buf=HBufC8::NewLC(size()); // this line allocates a descriptor which can contain the specified size, but it can be larger in fact
TPtr8 ptr( const_cast<TUint8*>(&(*buf)[0]), size()); // there are a number of equally ugly approaches you could choose from
socket.Read(ptr,size);
User::WaitForRequest(stat);
User::LeaveIfError(stat);

RDesReadStream stream;
stream.Open(*buf);
stream.PushL();
// deserialize your data
CleanupStack::PopAndDestroy(2); // stream, buf

Or an alternative would be RecvOneOrMore-ing in a loop, and collecting the data (in a CBufFlat for example) until the specified length has been reached.

[garrygar]

Hi,

Thanks for the detailed instructions. Yes you are right that the filename varies. But if I am able to read one hard-coded file name or directory name then I would be on track and can (hopefully) extend it from there on.

Anyway, in the solution you have provided, would I need to build (sender side )and parse (receiver side) the data i.e. the file name or will serialize and deserialize work the same thing for me? Second is there any Externalize/Internalize functions available in some API in S60/Symbian or do I have to implement my own serialize/deserialize functions? If I have to implement my own, could you give some hint/clue/idea/sample code?

Thanks

Garry