Send Image using forge packets?

[DarkGuardsman]

Is it possible to send an image using forge packet system. I have managed to download images using buffer streams and such using urls. However the only way i can get files download from my server mod is using ftp connection which need a password and username. problem with this is not every server owner will want to share there ftp password and username with every client. So i had an idea why not just send the image from the server instead of downloading from the server. Since forge has a built in system for passing data to the client why not see if i could use that. Is it even possible or do i have to make my own system for doing it.

[LexManos]

You can, I wouldnt, but you can.

Images are only data, MC doesnt care what data you send.

[calclavia]

Why don't you send a reference to the image for example a URL instead? Takes less memory.

[DarkGuardsman]

Why don't you send a reference to the image for example a URL instead? Takes less memory.

Yes but i'm trying to have a folder server side that contains custom Guard texture for each server instance. I can get them to download using a url just fine but i don't want to have servers need to host there images else where. In other word make it simple by having a folder that the mod read the image from and sends it too the client to be saved. Though i'm not sure how to do this now, i though about using forge packet system but how do i tell the client which image i'm sending it? Should i make the client request the image then the server send it to the client. The client expecting it would save it as the correct image?

[gcewing]

I think Minecraft already does something like this when it downloads player skins -- you might like to look into how it does that.

 

In any case, it's certainly possible -- you can put whatever data you want in a packet, including image data. I wouldn't try to download megabyte-sized files this way, since that might put rather a lot of load on the server, but small images should be fine.

 

As for the protocol, having the client request it from the server is probably best, especially if you're cacheing it in a local disk file, since the client can skip it if it already has the image.